Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Akka.Cluster.Tools: fix mutability and oldest state bugs with ClusterSingletonManager #7298

Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ public ClusterSingletonRestart2Spec(ITestOutputHelper output) : base("""
akka.loglevel = INFO
akka.actor.provider = "cluster"
akka.cluster.roles = [singleton]
#akka.cluster.auto-down-unreachable-after = 2s
akka.cluster.split-brain-resolver.stable-after = 2s
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug fixes for this spec - after doing a thorough review of some the cases where we had a race condition, it all comes down to whether or not _sys1 was able to fully get MemberRemoved or whether or not it became Unreachable first. Speeding up the downing provider's decision-making process both ensures that this member gets removed quickly AND ensures that the number of retries during the HandOver process get capped so the test can complete on-time.

akka.cluster.singleton.min-number-of-hand-over-retries = 5
akka.remote {
dot-netty.tcp {
Expand Down Expand Up @@ -120,7 +120,7 @@ await WithinAsync(TimeSpan.FromSeconds(5), () =>
await Join(_sys4, _sys3);

// let it stabilize
//Task.Delay(TimeSpan.FromSeconds(5)).Wait();
await Task.Delay(TimeSpan.FromSeconds(5));

await WithinAsync(TimeSpan.FromSeconds(10), () =>
{
Expand Down
Loading