The whole cluster will fail if the DC (crm daemon) is frozen due to CPU
starvation or hanging while trying to perform a IO operation.
Please share some thoughts on this issue.
Regards,
Shermal Fernando
-Original Message-
From: Klaus Wenninger [mailto:kwenn...@redhat.com]
Sent:
On 09/06/2016 02:04 PM, Devin Ortner wrote:
> I have a 2-node cluster running CentOS 6.8 and Pacemaker with DRBD. I have
> been using the "Clusters from Scratch" documentation to create my cluster and
> I am running into a problem where DRBD is not failing over to the other node
> when one goes
Anyone that follows this mailing list at all has probably noticed that I’m
creating a 2-node HA iSCSI Target on RHEL 6 using Pacemaker/Corosync (and CMAN,
I guess) and the available tgt scsi tools to use as shared file system for some
Windows Server Failover Cluster nodes. After a great deal of
On Tue, Sep 6, 2016 at 1:04 PM, Devin Ortner <
devin.ort...@gtshq.onmicrosoft.com> wrote:
> Master/Slave Set: ClusterDBclone [ClusterDB]
> Masters: [ node1 ]
> Slaves: [ node2 ]
> ClusterFS (ocf::heartbeat:Filesystem):Started node1
>
As Digimer said, you really need fencing
On 2016-09-06 14:04, Devin Ortner wrote:
I have a 2-node cluster running CentOS 6.8 and Pacemaker with DRBD.
I have been using the "Clusters from Scratch" documentation to create my
cluster and I am running into a problem where DRBD is not failing over
to the other node when one goes down.
I
> no-quorum-policy: ignore
> stonith-enabled: false
You must have fencing configured.
CentOS 6 uses pacemaker with the cman plugin. So setup cman
(cluster.conf) to use the fence_pcmk passthrough agent, then setup
proper stonith in pacemaker (and test that it works). Finally, tell DRBD
to use
I have a 2-node cluster running CentOS 6.8 and Pacemaker with DRBD. I have been
using the "Clusters from Scratch" documentation to create my cluster and I am
running into a problem where DRBD is not failing over to the other node when
one goes down. Here is my "pcs status" prior to when it is
