[erlang-questions] gen_leader usage/pointers
Juan Jose Comellas
Thu Sep 23 14:23:24 CEST 2010
Thanks for the data. I'd really prefer to be able to dynamically assign or
remove new nodes to the cluster. It's not entirely critical, but it would be
very uncomfortable if I had to restart the cluster in order to modify the
list of nodes (i.e. I don't want to wake up at 4:00 AM to do it).
On Wed, Sep 22, 2010 at 7:52 PM, Piotr Kaleta <piotrek.kaleta@REDACTED>wrote:
> First of all, few (if not all) versions of gen_leader implementations
> has been gathered on github here:
> As README says, you should use the 'combined_version'.
> A good starting point with tutorial is located at:
> However you should remember that current versions of gen_leader works in
> a way that you have to statically define the list of nodes that can
> become master in case of other nodes failure. Current implementations
> however, are incapable of adding nodes that might claim master role in
> future, at runtime. This makes gen_leader incapable of working in
> unstable environments when all of master nodes might go down for some
> On 09/23/2010 12:15 AM, Juan Jose Comellas wrote:
> > Can anyone who's ever used or (even better!) written one of the many
> > gen_leader incarnations point me to some documentation/examples on how to
> > use it? I have a scenario where I have to keep a master process (to be
> > chosen randomly or according to load) with slaves that takeover when the
> > master goes down. I'm not sure if gen_leader is the correct solution, as
> > master communicates to an external service and there will be more than
> > Both the master and the slave have open sockets to the external service
> > the slave socket is "activated" as soon as the master goes down.
> > I'd appreciate any pointers anybody might give me.
> > Thanks,
> > Juanjo
> erlang-questions (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:erlang-questions-unsubscribe@REDACTED
More information about the erlang-questions