[erlang-questions] Best implementation for a clustered connected client list ?

Morgan Segalis msegalis@REDACTED
Thu May 30 17:38:04 CEST 2013

Hi everyone,

I'm currently looking for better ways to do a clustered connected client list.

On every server I have an ets table, in which I insert / delete / search the process of each client connecting to the server.

Each row in the ets table is for now a simple {"id", <pid.of.process>}

I have tried the gproc module from Ulf Wiger, but when a cluster goes down, everything goes wrong… (especially if it is the elected leader).

If a cluster goes down, other clusters should consider that every client connected on the said cluster are actually not connected (even if is just a simple connection error between clusters).
If it goes back online, back on the nodes() list, other clusters should consider clients on this cluster back online.

What would be in your opinion the best way to do that ?

It is a messaging system, so it has to handle massive message passing through processes.

Thank you for your help.


More information about the erlang-questions mailing list