On Thu, Nov 5, 2009 at 7:32 PM, Andrew Beekhof <[email protected]> wrote: > On Thu, Nov 5, 2009 at 4:25 PM, Colin <[email protected]> wrote: >> On Wed, Oct 21, 2009 at 2:57 PM, Andrew Beekhof <[email protected]> wrote: >>> On Wed, Oct 21, 2009 at 1:48 PM, Colin <[email protected]> wrote: >>>> Let's see whether I can summarise correctly: >>> >>> basically all correct >>> >>>> For Pacemaker + CoroSync/OpenAIS, the Pacemaker attribute >>>> "expected-quorum-votes" tells the cluster how many votes it needs for >>>> quorum. (What happens when the option is not set?) >>> >>> The cluster sets it for you based on how many nodes it can see. >> >> Something strange is going on here: >> >> - The cluster updates expected-quorum-votes even when I set it >> manually; this seems to happen whenever a node joins or leavs the >> cluster. >> >> - A cluster with four expected-quorum-votes, and three of four nodes >> online, still has quorum; is this a bug??? Or is expected-quorum-votes >> not the number of nodes required in a partition to have quorum? > > no, its the total number of nodes seen by the cluster. > the cluster wont allow you to set this to a value less than the number > of nodes it knows about
Great, with that settled I can report that our 1.0.6 w/corosync cluster survived the first round of testing with no problems! Regards, Colin _______________________________________________ Pacemaker mailing list [email protected] http://oss.clusterlabs.org/mailman/listinfo/pacemaker
