On Fri, May 27, 2011 at 1:46 PM, Serge Dubrouski <serge...@gmail.com> wrote:
> > > On Fri, May 27, 2011 at 1:39 PM, "Roman Schartlmüller" < > roman_schartlmuel...@gmx.at> wrote: > >> >> -------- Original-Nachricht -------- >> > Datum: Fri, 27 May 2011 20:30:47 +0200 >> > Von: Jelle de Jong <jelledej...@powercraft.nl> >> > An: pacemaker@oss.clusterlabs.org >> > Betreff: Re: [Pacemaker] corosync-quorumtool configuration >> >> > On 27-05-11 18:19, Roman Schartlmüller wrote: >> > > Can anybody please help me with configuration? Maybe there is >> something >> > > wrong. >> > >> > Maybe lose the "no-quorum-policy=ignore" options. And a html mail with >> > tables really :D >> > >> > Kind regards, >> > >> > Jelle de Jong >> > >> Sorry, I did not know that html emails are unwanted. no-quorum-policy = >> "ignore" means that the node should not worry about the loss of quorum. But >> the quorum is lost anyway. >> >> I would like to know how to increase the votes of a node. Somehow, the >> value remains to 1. >> > > I don't think that that feature of Cororsync is supported by Pacemaker. I > can be wrong here. So far the rule of thumb was: 2 nodes cluster never has a > quorum, add one more node. > And if you think more it shouldn't work in 2 nodes cluster. Let's say you set up one node with 1 vote another node with 2 votes and expected votes set to 2 as well. Now pretend that your node with 2 votes dies. You loose your cluster in this way. Using nodes with number of votes higher than 1 makes sense for clusters with even numbers of nodes that can be split equally. Then partition that includes the node with higher number of votes wins. > > >> >> May 27 21:13:16 corosync [pcmk ] info: config_find_init: Local handle: >> 4835695805891346437 for quorum >> May 27 21:13:16 corosync [pcmk ] info: config_find_next: Processing >> additional quorum options... >> May 27 21:13:16 corosync [pcmk ] info: get_config_opt: Found >> 'corosync_votequorum' for option: provider >> May 27 21:13:16 corosync [pcmk ] info: update_member: Node Node1 now has >> 1 quorum votes (was 0) >> May 27 21:13:16 corosync [QUORUM] Using quorum provider >> corosync_votequorum >> May 27 21:13:16 corosync [SERV ] Service engine loaded: corosync votes >> quorum service v0.91 >> May 27 21:13:16 corosync [SERV ] Service engine loaded: corosync cluster >> quorum service v0.1 >> May 27 21:13:18 corosync [VOTEQ ] quorum regained, resuming activity >> May 27 21:13:18 corosync [pcmk ] info: update_member: Node Node2 now has >> 1 quorum votes (was 0) >> -- >> Mit freundlichen Grüßen >> >> Roman Schartlmüller >> >> NEU: FreePhone - kostenlos mobil telefonieren! >> Jetzt informieren: http://www.gmx.net/de/go/freephone >> >> _______________________________________________ >> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >> > > > > -- > Serge Dubrouski. > -- Serge Dubrouski.
_______________________________________________ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
