gen leader

Thomas Arts <>
Wed May 5 11:53:09 CEST 2004


Dear Martin

I am very glad to read that you can actually use the gen_leader code
and that it works fine for you. A while ago I posted a warning that there
still is a bug in the code that might cause you a daedlock, but we are
near to having a fix for that. New code has been written based on a
different algorithm (Scott D Stroller, "Leader Election in Distributed
Systems
with Crash Failures, 1997). We are verifying the code at the moment,
not to make the same mistake again :0).

The reason why we excluded the one node case for the leader
election algorithm is that we saw it as an implementation to
support fault tolerance. In case of 1 node, there is no fault
tolerance and a leader election for it seemed useless to us.

Best regards
Thomas


---
Dr Thomas Arts
     Program Manager
     Software Engineering and Management
IT-university in Gothenburg
Box 8718, 402 75 Gothenburg, Sweden
http://www.ituniv.se/

Tel +46 31 772 6031
Fax +46 31 772 4899


----- Original Message ----- 
From: "Martin J. Logan" <>
To: <>
Sent: Tuesday, May 04, 2004 6:31 PM
Subject: gen leader


> This message is directed at the authors of gen_leader. I have been
> playing with the gen_leader code of jungerl fame. This code is just what
> is needed obviate all of our "global" problems. I do have one question
> about the gen_leader code. If I start a gen_leader in a node cluster
> consisting of a single node() the single gen_leader process will not
> elect itself leader. I have to fake it by saying
> gen_leader:start_link(leader, [node(), fake_node], [],
> gen_leader_callback, Args, Options).
>
> What is the reason that gen_leader wants another gen_leader to dominate
> and is not content to be his own boss:-)
>
> Cheers,
> Martin
>
> P.S how does jungerl become erlpan i.e more people know, love, and use
> it?
>
>




More information about the erlang-questions mailing list