Dear hAkkers, 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 About that Windows TCP Workaround The underlying issue is that without signaling read interest on a connection Windows does not signal connection aborts, which means that in the absence of data traffic an abort may go unnoticed. The workaround (which can still be enabled but defaults to “off” now) always made sure to signal the right interest to reliably get this notification, but in some scenarios this will lead to a selector doing busy spinning—pegging one core to 100%. Since this behavior was reported more often than the missing abort notifications we decided to switch the default setting. If your program uses Akka IO and relies on TCP abort notifications when deployed on Windows you may want to manually enable the workaround. In a later release we will implement a better workaround that detects connection aborts but avoids the busy spinning selector loop. General Notices This release is binary backwards compatible with previous releases of the 2.3 series which means that it is a drop-in replacement for any older version—but not the other way around. Please make sure to always use the latest patch release even when other libraries declare a dependency on an older version of the 2.3 series. The complete list of closed tickets can be found in the 2.3.10 github issues milestone <https://github.com/akka/akka/issues?q=milestone%3A2.3.10>. For the full stats see the announcement on the website <http://akka.io/news/2015/04/23/akka-2.3.10-released.html>. Happy hakking! -- Patrik Nordwall Typesafe <http://typesafe.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
