You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+28-1
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,31 @@
1
-
#### 1.4.10 August 20th 2020 ####
1
+
#### 1.4.11 November 5 2020 ####
2
+
**Maintenance Release for Akka.NET 1.4**
3
+
4
+
Akka.NET v1.4.11 includes some significant additions to Akka.NET:
5
+
6
+
*[Akka: How prevent "Scheduled sending of heartbeat was delayed" and occasionally network partitions](https://github.com/akkadotnet/akka.net/issues/4432) - all `/system` actors now run on a dedicated dispatcher. This should significantly improve reliablity for Akka.Cluster, Akka.Persistence, and other built-in Akka.NET systems inside heavily utilized environments.
7
+
*[Akka: Double wildcard implementation for ActorSelection](https://github.com/akkadotnet/akka.net/pull/4375)
8
+
*[Akka.Remote: Null reference exception due to RemoteActorRefProvider.RemoteInternals](https://github.com/akkadotnet/akka.net/issues/4579)
9
+
*[Akka.Persistence: Fix premature reset of the 'writeInProgress' flag in case of persistence failure](https://github.com/akkadotnet/akka.net/pull/4556)
*[Cluster - Add app-version to the Member information](https://github.com/akkadotnet/akka.net/pull/4577) - you can now specify which version of your software is running on each node.
12
+
*[Akka.Cluster.Sharding: Bring ShardedDaemonProcess up to date](https://github.com/akkadotnet/akka.net/pull/4571)
13
+
14
+
To see the [full set of fixes in Akka.NET v1.4.11, please see the milestone on Github](https://github.com/akkadotnet/akka.net/milestone/42).
15
+
16
+
| COMMITS | LOC+ | LOC- | AUTHOR |
17
+
| --- | --- | --- | --- |
18
+
| 8 | 1020 | 164 | Gregorius Soedharmo |
19
+
| 7 | 399 | 178 | Ismael Hamed |
20
+
| 4 | 5 | 5 | dependabot-preview[bot]|
21
+
| 4 | 108 | 104 | Aaron Stannard |
22
+
| 2 | 232 | 26 | to11mtm |
23
+
| 2 | 2 | 2 | Pierre Irrmann |
24
+
| 2 | 1969 | 269 | zbynek001 |
25
+
| 2 | 155 | 445 | huysentruitw |
26
+
| 1 | 1 | 1 | Guillaume Caya-Letourneau |
27
+
28
+
#### 1.4.10 August 20 2020 ####
2
29
**Maintenance Release for Akka.NET 1.4**
3
30
4
31
Akka.NET v1.4.10 includes some minor bug fixes and some major feature additions to Akka.Persistence.Query:
Some dispatcher configurations are available out-of-the-box for convenience. You can use them during actor deployment, [as described above](#configuring-dispatchers).
71
71
72
72
***default-dispatcher** - A configuration that uses the [ThreadPoolDispatcher](#threadpooldispatcher). As the name says, this is the default dispatcher configuration used by the global dispatcher, and you don't need to define anything during deployment to use it.
73
+
***internal-dispatcher** - To protect the internal Actors that is spawned by the various Akka modules, a separate internal dispatcher is used by default.
73
74
***task-dispatcher** - A configuration that uses the [TaskDispatcher](#taskdispatcher).
74
75
***default-fork-join-dispatcher** - A configuration that uses the [ForkJoinDispatcher](#forkjoindispatcher).
75
76
***synchronized-dispatcher** - A configuration that uses the [SynchronizedDispatcher](#synchronizeddispatcher).
@@ -174,3 +175,10 @@ The following configuration keys are available for any dispatcher configuration:
174
175
175
176
> [!NOTE]
176
177
> The throughput-deadline-time is used as a *best effort*, not as a *hard limit*. This means that if a message takes more time than the deadline allows, Akka.NET won't interrupt the process. Instead it will wait for it to finish before giving turn to the next actor.
178
+
179
+
## Dispatcher aliases
180
+
181
+
When a dispatcher is looked up, and the given setting contains a string rather than a dispatcher config block,
182
+
the lookup will treat it as an alias, and follow that string to an alternate location for a dispatcher config.
183
+
If the dispatcher config is referenced both through an alias and through the absolute path only one dispatcher will
Copy file name to clipboardExpand all lines: docs/articles/persistence/persistence-query.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ The predefined queries are:
50
50
51
51
**AllPersistenceIdsQuery (PersistentIds) and CurrentPersistenceIdsQuery**
52
52
53
-
`AllPersistenceIds`, or `PersistenceIds`in `IPersistenceIdsQuery`, is used to retrieve all cached persistenceIds of all persistent actors inside the `ActorSystem` where the journal actor is instantiated. Note that since this is a cached value, this query will only report `PersistentIds` that passed to the journal since the journal creation time (local cache).
53
+
`AllPersistenceIds` or `PersistenceIds`, and `CurrentPersistenceIds`in `IPersistenceIdsQuery` is used for retrieving all persistenceIds of all persistent actors.
54
54
55
55
```csharp
56
56
varqueries=PersistenceQuery.Get(actorSystem)
@@ -64,7 +64,7 @@ The returned event stream is unordered and you can expect different order for mu
64
64
65
65
The stream is not completed when it reaches the end of the currently used `PersistenceIds`, but it continues to push new `PersistenceIds` when new persistent actors are created. Corresponding query that is completed when it reaches the end of the currently used `PersistenceIds` is provided by `CurrentPersistenceIds`.
66
66
67
-
The write journal is notifying the query side as soon as new `PersistenceIds` are created and there is no periodic polling or batching involved in this query.
67
+
Periodic polling of new `PersistenceIds` are done on the query side by retrieving the events in batches that sometimes can be delayed up to the configured `refresh-interval` or given `RefreshInterval` hint.
68
68
69
69
The stream is completed with failure if there is a failure in executing the query in the backend journal.
Copy file name to clipboardExpand all lines: docs/articles/remoting/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ akka {
97
97
See [Akka Remote Reference Config File](https://github.com/akkadotnet/akka.net/blob/dev/src/core/Akka.Remote/Configuration/Remote.conf) for additional information on HOCON settings available in akka remote.
98
98
99
99
## Addresses, Transports, Endpoints, and Associations
100
-
In the above section we mentioned that you have to bind a *transport* to an IP address and port, we did in that in HOCON inside the `dot-netty.tcp` section. Why did we have to do any of that?
100
+
In the above section we mentioned that you have to bind a *transport* to an IP address and port, we did that in HOCON inside the `dot-netty.tcp` section. Why did we have to do any of that?
101
101
102
102
Well, let's take a step back to define some key terms you'll need to be familiar with in order to use Akka.Remote:
Copy file name to clipboardExpand all lines: docs/articles/utilities/circuit-breaker.md
+11-16
Original file line number
Diff line number
Diff line change
@@ -16,25 +16,20 @@ The Akka.NET library provides an implementation of a circuit breaker called `Akk
16
16
## What do they do?
17
17
18
18
* During normal operation, a circuit breaker is in the `Closed` state:
19
-
* Exceptions or calls exceeding the configured `СallTimeout` increment a
20
-
failure counter
21
-
* Successes reset the failure count to zero
22
-
* When the failure counter reaches a `MaxFailures` count, the breaker is
23
-
tripped into `Open` state
19
+
* Exceptions or calls exceeding the configured `СallTimeout` increment a failure counter
20
+
* Successes reset the failure count to zero
21
+
* When the failure counter reaches a `MaxFailures` count, the breaker is tripped into `Open` state
24
22
* While in `Open` state:
25
-
* All calls fail-fast with a `OpenCircuitException`
26
-
* After the configured `ResetTimeout`, the circuit breaker enters a
27
-
`Half-Open` state
23
+
* All calls fail-fast with a `OpenCircuitException`
24
+
* After the configured `ResetTimeout`, the circuit breaker enters a `Half-Open` state
28
25
* In `Half-Open` state:
29
-
* The first call attempted is allowed through without failing fast
30
-
* All other calls fail-fast with an exception just as in `Open` state
31
-
* If the first call succeeds, the breaker is reset back to `Closed` state
32
-
* If the first call fails, the breaker is tripped again into the `Open` state
33
-
for another full `ResetTimeout`
26
+
* The first call attempted is allowed through without failing fast
27
+
* All other calls fail-fast with an exception just as in `Open` state
28
+
* If the first call succeeds, the breaker is reset back to `Closed` state and the `ResetTimeout` is reset
29
+
* If the first call fails, the breaker is tripped again into the `Open` state (as for exponential backoff circuit breaker, the `ResetTimeout` is multiplied by the exponential backoff factor)
34
30
* State transition listeners:
35
-
* Callbacks can be provided for every state entry via `OnOpen`, `OnClose`,
36
-
and `OnHalfOpen`
37
-
* These are executed in the `ExecutionContext` provided.
31
+
* Callbacks can be provided for every state entry via `OnOpen`, `OnClose`, and `OnHalfOpen`
32
+
* These are executed in the `ExecutionContext` provided.
<PackageReleaseNotes>Placeholder for nightlies**</PackageReleaseNotes>
31
+
<PackageReleaseNotes>Maintenance Release for Akka.NET 1.4**
32
+
Akka.NET v1.4.11 includes some significant additions to Akka.NET:
33
+
[Akka: How prevent "Scheduled sending of heartbeat was delayed" and occasionally network partitions](https://github.com/akkadotnet/akka.net/issues/4432) - all `/system` actors now run on a dedicated dispatcher. This should significantly improve reliablity for Akka.Cluster, Akka.Persistence, and other built-in Akka.NET systems inside heavily utilized environments.
34
+
[Akka: Double wildcard implementation for ActorSelection](https://github.com/akkadotnet/akka.net/pull/4375)
35
+
[Akka.Remote: Null reference exception due to RemoteActorRefProvider.RemoteInternals](https://github.com/akkadotnet/akka.net/issues/4579)
36
+
[Akka.Persistence: Fix premature reset of the 'writeInProgress' flag in case of persistence failure](https://github.com/akkadotnet/akka.net/pull/4556)
[Cluster - Add app-version to the Member information](https://github.com/akkadotnet/akka.net/pull/4577) - you can now specify which version of your software is running on each node.
39
+
[Akka.Cluster.Sharding: Bring ShardedDaemonProcess up to date](https://github.com/akkadotnet/akka.net/pull/4571)
40
+
To see the [full set of fixes in Akka.NET v1.4.11, please see the milestone on Github](https://github.com/akkadotnet/akka.net/milestone/42).
0 commit comments