Re: [ClusterLabs] [EXT] DRBD 2-node M/S doesn't want to promote new master, Centos 8

On 1/15/21 10:10 PM, Brent Jensen wrote: pacemaker-attrd[7671]: notice: Setting master-drbd0[nfs5]: 1 -> 1000 I wonder: Does that mean the stickiness for master is still 1000 on nfs5? ___ Manage your subscription:

[ClusterLabs] DRBD 2-node M/S doesn't want to promote new master, Centos 8

Problem: When performing "pcs node standby" on the current master, this node demotes fine but the slave doesn't promote to master. It keeps  looping the same error including "Refusing to be Primary while peer is  not outdated" and "Could not connect to the CIB." At this point the old  master

[ClusterLabs] What's a "transition", BTW?

Hi! With a cluster recheck interval, I see periodic log messages like this: Jan 15 11:05:50 h19 pacemaker-controld[4804]: notice: State transition S_TRANSITION_ENGINE -> S_IDLE Jan 15 11:15:50 h19 pacemaker-controld[4804]: notice: State transition S_IDLE -> S_POLICY_ENGINE Jan 15 11:15:50 h19

[ClusterLabs] Q: placement-strategy=balanced

Hi! The cluster I'm configuring (SLES15 SP2) fenced a node last night. Still unsure what exactly caused the fencing, but looking at the logs I found this "action plan" that lead to fencing: Jan 14 20:05:12 h19 pacemaker-schedulerd[4803]: notice: * Move prm_cron_snap_test-jeos1