On 4/19/2013 12:00 PM, Ferenc Wagner wrote:
> Hi!
>
> I'm building a Pacemaker cluster on top of Corosync 1.4.2. I started
> with 3 nodes, so their corosync.conf files contain:
>
> quorum {
> provider: corosync_votequorum
> expected_votes: 3
> }
>
> Now I'm adding a new node, which has a very similar configuration, but
> with expected_votes: 4. My question: what happens in a cluster where
> the nodes have different values for expected_votes? The new node joined
> the cluster all right, and crm status reports:
>
> 4 Nodes configured, 4 expected votes
>
> on all nodes (even on those with expected_votes: 3). This seems just
> fine, but I fear I might be hit by unobvious repercussions later. I can
> restart corosync on the other nodes after adjusting their config, but
> sooner of later I'll be in a similar situation again...
>
votequorum is not supported in 1.4.x series.
You want to upgrade to corosync 2.3.x.
expected_votes on running nodes will be automatically upgraded to 4. you
want to make sure to update corosync.conf too to make sure that at the
next restart the node will rejoin with the runtime value.
There are no other repercussions.
You only have to be a bit more careful when removing nodes. If you are
only adding it´s not a problem.
Fabio
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
