Topology change stops manually registered processes on another nodes - Githubissues

bitwalker / swarm

Easy clustering, registration, and distribution of worker processes for Erlang/Elixir

MIT License

1.19k stars 102 forks source link

Topology change stops manually registered processes on another nodes #57

Closed gofoss closed 6 years ago

gofoss commented 6 years ago

Hello!

I am using Swarm 3.0.5 with libcluster. Imagine, I have two nodes starting up.

On every node startup same procedure is invoked:

Swarm.whereis_name to see if name is registered
if not, start GenServer using via tuple
try to register with Swarm.register_name/2

NodeA starts up and follows procedure and registers new process NodeB follows same procedure, but as soon as Swarm application starts on the NodeB, before even proceeding to my custom logic, on NodeA I get the following in debug log level:

topology change (nodeup....)
removing registration for XXXX, nodeA is down

even though nodeA is up and after that I can run Swarm.registered/0 and see process registered on NodeB.

Any thoughts about this behavior?

Thanks!

bitwalker commented 6 years ago

Definitely a bug if still happening. Have you tried recent releases? Is this still an issue?

gofoss commented 6 years ago

I think, this was mis-configuration issue on my side. Thanks for following it up.