Hi Yusuke, Sorry for the late reply;)
On Mon, 2013-01-07 at 13:50 +0900, yusuke iida wrote: > Hi, Jiaju > > When the proposal was conflict, I want to keep on the site of the > original lease. > I do not want to generate a revoke when maintained. > > > I made a patch according to a thought of "5.2 Master lease" described > in the next article. > It means that it prevents you from accepting new suggestion until a > time limit of lease expires. Exactly. > > http://www.read.seas.harvard.edu/~kohler/class/08w-dsi/chandra07paxos.pdf > > Is there anything wrong with this idea? This idea is totally right. But we have already implemented it. When the master exists and is still in its lease, if some other one wants to be the master and sent the "prepare" message, the acceptor will told him "oh, we have already had a master" by setting "hdr->leased = 1" in his respond message, actually this is a rejection, then the one trying to be master won't succeed. It seems your patch is also doing this, right? Thanks, Jiaju _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
