Thank you Christine and Andrei,
I took a look at the corosync quorum policy configuration options, and
actually I would need a more conservative approach, i.e. to consider quorum
only if all the nodes are present - any node loss is a quorum loss event
for me. At present I check it in an agent,
On 09/11/15 22:20, Radoslaw Garbacz wrote:
> Hi,
>
> I have a question regarding the policy to check for cluster quorum for
> corosync+pacemaker.
>
> As far as I know at present it is always (excpected_votes)/2 + 1. Seems
> like "qdiskd" has an option to change it, but it is not clear to me if
>
Hi,
I have a question regarding the policy to check for cluster quorum for
corosync+pacemaker.
As far as I know at present it is always (excpected_votes)/2 + 1. Seems
like "qdiskd" has an option to change it, but it is not clear to me if
corosync 2.x supports different quorum device.
What are
On Tue, Nov 10, 2015 at 1:20 AM, Radoslaw Garbacz
wrote:
> Hi,
>
> I have a question regarding the policy to check for cluster quorum for
> corosync+pacemaker.
>
> As far as I know at present it is always (excpected_votes)/2 + 1. Seems like
> "qdiskd" has an