> On 29 Oct 2014, at 7:48 pm, Andrei Borzenkov wrote:
>
> On Wed, Oct 29, 2014 at 10:46 AM, Ariel S wrote:
>> Hello,
>>
>> I'm trying to understand how this STONITH works.
>>
>> I have 2 VMware VMs (moon1a, moon1b) on two different hosts. Each have 2 nic
>> assigned: eth0 for heartbeat while
Thank you for the reply, I try severing the heartbeat nic and add set the
`no-quorum-policy` to `ignore` (I forgot that one) like this:
# crm configure property no-quorum-policy=ignore
and it works nicely.
Thank you,
Ariel
On 10/29/2014 03:27 PM, Sven Moeller wrote:
You can try to force
On Wed, Oct 29, 2014 at 10:46 AM, Ariel S wrote:
> Hello,
>
> I'm trying to understand how this STONITH works.
>
> I have 2 VMware VMs (moon1a, moon1b) on two different hosts. Each have 2 nic
> assigned: eth0 for heartbeat while eth1 used for everything else.
>
> This is my testing configuration:
You can try to force a split brain by shutting down the heartbeat NICs and keep
corosync running on both nodes.
Regards Sven
Ariel S schrieb:
>Hello,
>
>I'm trying to understand how this STONITH works.
>
>I have 2 VMware VMs (moon1a, moon1b) on two different hosts. Each have 2 nic
>assigned: e
