Akka 2.3.10 Maintenance Release
We—the Akka committers—are pleased to be able to announce the availability of Akka 2.3.10. This is the tenth maintenance release of the 2.3 branch. This release contains several important improvements:
- change default configuration to disable TCP IO connection abort workaround on windows (see more below)
- fix open-coded spinlock in DirectByteBufferPool, which could result in CPU spikes for some workloads
- remove wrong assertion in remoting, which could lead to ActorSystem termination when restarted remote ActorSystem connects after being quarantined
- fix issue in remoting that allocates new socket for each unsuccessful connection attempt to a quarantined system
- fix issue in remoting to not terminate connections if quarantine id do not match, which could result in that cluster node cannot join after restart
- fix issue in ClusterSharding, when coordinator node gracefully leaves the cluster it could save invalid information about the shard locations
- fix memory leak with watch and ask involved
- fix inconsistent cluster metrics
- fix IllegalStateException in akka.dispatch.BatchingExecutor
- fix issue in clustering to exclude unreachable observations from downed node so that leader can perform its duties independent of downed nodes
- report cause of bind and connect failures
- add support for cluster member joining again after restart without having to down and remove the old member with same hostname and port
The complete list of closed tickets can be found in the 2.3.10 github issues milestone.
For the full stats see the announcement on the website.