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

DeliveryManagerMultiNodeSpecs: node that restarts is actually a different node #12

Open
Aaronontheweb opened this issue Jul 28, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@Aaronontheweb
Copy link
Member

await WithinAsync(TimeSpan.FromSeconds(10), async () =>
{
var cluster1 = Akka.Cluster.Cluster.Get(Sys);
Shutdown(Sys2);
await AwaitConditionAsync(() => cluster1.State.Members.Count == 2);
});
// have Sys message Sys3 (validate that we didn't break connections to healthy nodes)
var msg2 = new ChunkedDelivery("hello2", probe3.Ref, probe.Ref);
dm1.Tell(msg2);
await probe3.ExpectMsgAsync("hello2");
probe3.Reply("ok2");
await probe.ExpectMsgAsync("ok2");
// restart Sys2
var newSys2 = ActorSystem.Create(Sys.Name, Sys.Settings.Config);
var dm2New = CreateDeliveryManager(newSys2);
var probe2New = CreateTestProbe(newSys2);

Node 2 restarts on port 0, making it effectively a different node - we need to grab the Cluster.SelfAddress for node2 and inject that into its akka.remote.dot-netty.tcp.port setting to ensure we're reusing the previous address.

@Aaronontheweb Aaronontheweb added the bug Something isn't working label Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant