Akka Resilience Enhancements Release Notes

Version 1.1.14

  • Kubernetes Lease released also for Scala 2.13
  • Minimum versions of Akka updated to 2.5.26 or 2.6.4

Version 1.1.13

Version 1.1.12

  • Support Akka 2.6.x and 2.5.x.
  • Make Config Checker compatible with Akka 2.6.x and 2.5.x.
  • Make Fast Failover compatible with Akka 2.6.x and 2.5.x.

Version 1.1.11

  • Add sensitive config paths for cassandra, jdbc and couchbase Persistence plugins
  • Update link to credentials for dependencies

Version 1.1.10

  • Added support for running under Scala 2.13.0
  • Improved documentation for Kubernetes Lease
  • Fixed false positive in config checker about “akka.actor.default-dispatcher.fork-join-executor.task-peeking-mode”

Version 1.1.9

Version 1.1.8, March 13, 2019

Version 1.1.7, January 4, 2019

  • Updated dependencies to Akka 2.5.19 and akka-persistence-cassandra 0.92, which also updates the transitive dependency to Guava (older version has security vulnerability)

Version 1.1.6, December 18, 2018

  • New SBR down-all strategy. This strategy can be a safe alternative if the network environment is highly unstable with unreachability observations that can’t be fully trusted, and including frequent occurrences of indirectly connected nodes. In such environments it can be better to shutdown all nodes and start up a new fresh cluster. See Down All documentation.
  • New SBR configuration property down-all-when-unstable to down all nodes if failure detector observations continue to change for too long. Down all when unstable documentation.
  • New SBR configuration property keep-one-indirectly-connected to allow downing of all indirectly connected nodes instead of keeping one, which can be a safer option in unstable environments. See Indirectly connected nodes documentation.
  • Highlight and clarify the scenarios that can lead to SBR decisions that result in forming separate clusters, i.e. the system will experience a split brain scenario.

Version 1.1.5, November 23, 2018

  • New SBR algorithm to handle scenarios where nodes are marked as unreachable via some network links but they are still indirectly connected via other nodes, i.e. it’s not a clean network partition (or node crash). See Indirectly connected nodes documentation.

Version 1.1.4, November 8, 2018

  • Fix issue that SBR might not be active on nodes with status WeaklyUp
  • More SBR logging
  • Clarify SBR stable-after and down-removal-margin
  • Additional hints by Thread Starvation Detector what can be the cause of the problems