Re: [Pacemaker] Problems when quorum lost for a short period of time

2013-10-03 Thread Lev Sidorenko
On Wed, 2013-10-02 at 10:40 +0200, Lars Marowsky-Bree wrote: > On 2013-10-02T09:26:26, Lev Sidorenko wrote: > > > It is actually 2 nodes for main+stanby and another two nodes just for > > provide quorum. > > Like Andrew wrote, a third node would be enough for that purpose. > > You might as well

Re: [Pacemaker] Problems when quorum lost for a short period of time

2013-10-02 Thread Lars Marowsky-Bree
On 2013-10-02T09:26:26, Lev Sidorenko wrote: > It is actually 2 nodes for main+stanby and another two nodes just for > provide quorum. Like Andrew wrote, a third node would be enough for that purpose. You might as well run an iSCSI target on that node (instead of the full cluster stack) and use

Re: [Pacemaker] Problems when quorum lost for a short period of time

2013-10-01 Thread Andrew Beekhof
On 02/10/2013, at 6:26 AM, Lev Sidorenko wrote: > Hello All! > > I have a 4-nodes cluster setup. > > It is actually 2 nodes for main+stanby and another two nodes just for > provide quorum. 1 extra would have been enough > > So, all resources run on the main node but only DRBD-slave runs on

[Pacemaker] Problems when quorum lost for a short period of time

2013-10-01 Thread Lev Sidorenko
Hello All! I have a 4-nodes cluster setup. It is actually 2 nodes for main+stanby and another two nodes just for provide quorum. So, all resources run on the main node but only DRBD-slave runs on the standby node. I have no-quorum-policy="stop" So, sometimes main node looses connection to the