[ClusterLabs] Resource monitors crash, restart, leave core files

Hi folks, My test system, which includes support for a filesystem resource called 'mount', works fine otherwise, but every day or so I see monitor errors like the following when I run 'pcs status': Failed Resource Actions: * mount_monitor_2 on bd3c7 'unknown error' (1): call=23,

Re: [ClusterLabs] DRBD not failing over

Quoting Jaap Winius : Very interesting. I'm already running DRBD 9, so that base has already been covered, but here's some extra information: My test system actually consists of a single 4-node DRBD cluster that spans two data centers, with each data center having a 2-node Pacemaker

Re: [ClusterLabs] DRBD not failing over

Quoting "Nickle, Richard" : * Switch to DRBD 9 ... * Build a third diskless quorum arbitration node. Very interesting. I'm already running DRBD 9, so that base has already been covered, but here's some extra information: My test system actually consists of a single 4-node DRBD cluster

[ClusterLabs] DRBD not failing over

Hi folks, My 2-node test system has a DRBD resource that is configured as follows: ~# pcs resource defaults resource-stickiness=100 ; \ pcs resource create drbd ocf:linbit:drbd drbd_resource=r0 \ op monitor interval=60s ; \ pcs resource master drbd master-max=1 master-node-max=1

[ClusterLabs] Auto-failback prevention

(which is created by the "pcs resource move" command) the resources just stop and never fail over when the node goes down. So, how should the configuration below be altered to result only in failovers, while preventing failbacks from ever happening? Thanks, Jaap