Bump Akka from 1.4.18 to 1.4.19

[dependabot-preview]

⚠️ Dependabot Preview has been deactivated ⚠️

This pull request was created by Dependabot Preview, and you've upgraded to Dependabot. This means it won't respond to dependabot commands nor will it be automatically closed if a new version is found.

If you close this pull request, Dependabot will re-create it the next time it checks for updates and everything will work as expected.

---

Bumps Akka from 1.4.18 to 1.4.19.

Release notes

Sourced from Akka's releases.

Akka.NET v1.4.19

1.4.19 April 28 2021

Maintenance Release for Akka.NET 1.4

Akka.NET v1.4.19 is a substantial release that includes a number of critical Akka.Cluster fixes, baseline Akka.NET performance improvements, and entirely new dispatcher that has shown to improve performance when used across all of the major actor groups that run both inside the /user hierarchy and the /system actor hierarchy as well.

Akka.Cluster Improvements One of the most demanding issues of the v1.4.19 release was "Akka.Cluster: quarantining / reachability changes appear to be extremely sensitive" - and this is because debugging this issue touched so many different parts of Akka.Cluster.

We ultimately solved the problem - it is now quite feasible to rapidly scale an Akka.NET cluster from ~10 nodes to 50+ nodes without having a huge number of quarantines, accidentally downed nodes, and so on.

Here's the full set of fixes that went into resolving this issue:

• Added PhiAccrualFailureDetector warning logging for slow heartbeats
• measure Akka.Cluster heartbeat timings, hardened Akka.Cluster serialization
• ClusterStressSpec and Cluster Failure Detector Cleanup
• Akka.Cluster: improve HeartbeatNodeRing performance
• Akka.Cluster: Turned HeatbeatNodeRing into struct
• Akka.Cluster: Configure duration for applying MemberStatus.WeaklyUp to joining nodes
• Akka.Cluster: Performance optimize VectorClock
• Akka.Cluster: Refactored Gossip into MembershipState
• Akka.Remote: Clean up bad outbound ACKs in Akka.Remote

Akka.Cluster is now much more robust, faster, and capable of scaling up and down much more efficiently than in previous releases.

ChannelExecutor and Akka Performance Improvements In addition to improving Akka.Cluster, we also made substantial improvements to constructs found inside Akka.NET core itself:

• Perf optimize ActorSelection - 20% throughput improvement, 25% memory consumption improvement
• fixed N-1 error inside Mailbox
• Introduce ChannelExecutor

In Akka.NET v1.4.19 we introduce an opt-in feature, the ChannelExecutor - a new dispatcher type that re-uses the same configuration as a ForkJoinDispatcher but runs entirely on top of the .NET ThreadPool and is able to take advantage of dynamic thread pool scaling to size / resize workloads on the fly.

In order to get the most use out of the ChannelExecutor, the default actor dispatcher, the internal dispatcher, and the Akka.Remote dispatchers all need to run on it - and you can see the latest configuration settings and guidance for that here in our documentation: https://getakka.net/articles/actors/dispatchers.html#channelexecutor

But a copy of today's configuration is included below - you can enable this feature inside your Akka.NET applications via the following HOCON:

akka.actor.default-dispatcher = {
    executor = channel-executor
    fork-join-executor { #channelexecutor will re-use these settings
      parallelism-min = 2
      parallelism-factor = 1
      parallelism-max = 64
    }
}
akka.actor.internal-dispatcher = {
executor = channel-executor
</tr></table>

... (truncated)

Changelog

Sourced from Akka's changelog.

1.4.19 April 28 2021

Maintenance Release for Akka.NET 1.4

Akka.NET v1.4.19 is a substantial release that includes a number of critical Akka.Cluster fixes, baseline Akka.NET performance improvements, and entirely new dispatcher that has shown to improve performance when used across all of the major actor groups that run both inside the /user hierarchy and the /system actor hierarchy as well.

Akka.Cluster Improvements One of the most demanding issues of the v1.4.19 release was "Akka.Cluster: quarantining / reachability changes appear to be extremely sensitive" - and this is because debugging this issue touched so many different parts of Akka.Cluster.

We ultimately solved the problem - it is now quite feasible to rapidly scale an Akka.NET cluster from ~10 nodes to 50+ nodes without having a huge number of quarantines, accidentally downed nodes, and so on.

Here's the full set of fixes that went into resolving this issue:

• Added PhiAccrualFailureDetector warning logging for slow heartbeats
• measure Akka.Cluster heartbeat timings, hardened Akka.Cluster serialization
• ClusterStressSpec and Cluster Failure Detector Cleanup
• Akka.Cluster: improve HeartbeatNodeRing performance
• Akka.Cluster: Turned HeatbeatNodeRing into struct
• Akka.Cluster: Configure duration for applying MemberStatus.WeaklyUp to joining nodes
• Akka.Cluster: Performance optimize VectorClock
• Akka.Cluster: Refactored Gossip into MembershipState
• Akka.Remote: Clean up bad outbound ACKs in Akka.Remote

Akka.Cluster is now much more robust, faster, and capable of scaling up and down much more efficiently than in previous releases.

ChannelExecutor and Akka Performance Improvements In addition to improving Akka.Cluster, we also made substantial improvements to constructs found inside Akka.NET core itself:

• Perf optimize ActorSelection - 20% throughput improvement, 25% memory consumption improvement
• fixed N-1 error inside Mailbox
• Introduce ChannelExecutor

In Akka.NET v1.4.19 we introduce an opt-in feature, the ChannelExecutor - a new dispatcher type that re-uses the same configuration as a ForkJoinDispatcher but runs entirely on top of the .NET ThreadPool and is able to take advantage of dynamic thread pool scaling to size / resize workloads on the fly.

In order to get the most use out of the ChannelExecutor, the default actor dispatcher, the internal dispatcher, and the Akka.Remote dispatchers all need to run on it - and you can see the latest configuration settings and guidance for that here in our documentation: https://getakka.net/articles/actors/dispatchers.html#channelexecutor

But a copy of today's configuration is included below - you can enable this feature inside your Akka.NET applications via the following HOCON:

akka.actor.default-dispatcher = {
    executor = channel-executor
    fork-join-executor { #channelexecutor will re-use these settings
      parallelism-min = 2
      parallelism-factor = 1
      parallelism-max = 64
    }
}
akka.actor.internal-dispatcher = {
executor = channel-executor
throughput = 5
</tr></table>

... (truncated)

Commits

• 7a34a14 v1.4.19 Akka.NET Release (#4987)
• a3feeef added v1.4.19 release notes (#4985)
• 82d7909 Upgrade to GitHub-native Dependabot (#4984)
• bdfc893 Introduce ChannelExecutor (#4882)
• e58d36a Removed inaccurate warning from Cluster Singleton docs (#4980)
• a1fa221 Update PluginSpec so that it can accept ActorSystem and ActorSystemSetup in i...
• 101f5a2 fixed racy ActorModelSpec (#4976)
• d178b63 clean up seed node process (#4975)
• 321d0e4 ORDictionary with POCO value missing items, add MultiNode spec (#4910)
• 442f8eb Fix serialization verification problem with Akka.IO messages (#4974)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)