[erlang-questions] gproc_dist finicky about latecomers

Oliver Korpilla Oliver.Korpilla@REDACTED
Sat Jun 3 08:28:27 CEST 2017


I use gproc/gproc_dist with gen_leader_revival. I have the gproc_dist all application option on and do use global names.

It works fine if and only if I connect nodes first and then start gproc afterwards for additional nodes joining the cluster.

If I start gproc before connecting nodes, every node insists on being the leader (I queried through the gproc API for each node) and they stick with their opinion. global aggregated counters in turn do not work, failing my application's simple loadbalancing.

I ran into this problem twice:

* When originally writing my application startup.
* When redoing the startup and forgetting why I started gproc at a specific time.

I hoped to document this somehow.

Do people observe the same with locks_leader?


More information about the erlang-questions mailing list