Re: Corosync 2.0 split-brain avoidance

["Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx>]

Please keep the replies on the mail list so others can participate as well.

On 5/15/2012 9:42 AM, Voznesensky Vladimir wrote:
> On 15.05.2012 11:26, Fabio M. Di Nitto wrote:
>> On 5/15/2012 7:24 AM, Voznesensky Vladimir wrote:
>>> Hello.
>>>
>>> How to avoid split-brain of cluster software pieces in the lack of
>>> plugins?
>>> Maybe, how to configure cluster engines (pacemaker, gfs2, etc.) to use a
>>> single source of quorum?
>> You can use votequorum. man votequorum.5
>>
> If I understood correct, this fine manpage describes one instance of
> coresync per physical node architecture.

one node, one corosync instance.

> How could I use the same quorum machinery for pacemaker and my own
> application? Is it wise at all?

pacemaker (1.1.7 or higher) already use votequorum/quorum from corosync.

If you write your own application, then look into quorum_overview.8 and
quorum_*.3 man pages for description of the client side and library API.

Fabio
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss