Sounds useful, thanks. Might be something for a lighting talk? Judging by the amount of hex packages, perhaps even a Arjans toolbox-talk

Hi.
Thanks for putting the library together.

Before I found it, I’ve been trying to hack my own implementation and I ended up with a very similar code as yours.

However, both your code and mine suffers from an unexpected behavior.

When a 2nd node joins the cluster, I do see:

23:24:54.246 [info]  global: Name conflict terminating {:singleton, #PID<18487.303.0>}

But what is unexpected is that not only the singleton process is terminated, but the whole application on one of the nodes:

23:25:47.517 [info]  Application wpc5_singleton exited: killed

And one of the nodes basically is left in a state where my own application is not running, only the “libraries” continue running.

I’ve been struggling with the same issue in my own implementation.

I created a DynamicSupervisor for the singleton process, similarly to you and I was hoping that it will “shield” the main Application supervisor from crashing when the :global registry kills one of the singleton processes.

However, that doesn’t seem to be the case and the whole application dies regardless of multiple layers of supervisors

Using Elixir version 1.12.3

@bodgix have you managed to solve this issue? we’re facing the same problem

What is restart set to in the “singleton” GenServer? If it’s set to the default :permanent, then the supervisor on the joined node will keep restarting the process over and over again until it also gives up, cascading down the chain of supervisors until the whole application stops.

Does the behavior change if you specify use GenServer, restart: :temporary?