[ClusterLabs] drbd clone not becoming master

Dennis Jacobfeuerborn dennisml at conversis.de
Thu Nov 2 18:08:07 EDT 2017


Hi,
I'm setting up a redundant NFS server for some experiments but almost
immediately ran into a strange issue. The drbd clone resource never
promotes either of the to clones to the Master state.

The state says this:

 Master/Slave Set: drbd-clone [drbd]
     Slaves: [ nfsserver1 nfsserver2 ]
 metadata-fs	(ocf::heartbeat:Filesystem):	Stopped

The resource configuration looks like this:

Resources:
 Master: drbd-clone
  Meta Attrs: master-node-max=1 clone-max=2 notify=true master-max=1
clone-node-max=1
  Resource: drbd (class=ocf provider=linbit type=drbd)
   Attributes: drbd_resource=r0
   Operations: demote interval=0s timeout=90 (drbd-demote-interval-0s)
               monitor interval=60s (drbd-monitor-interval-60s)
               promote interval=0s timeout=90 (drbd-promote-interval-0s)
               start interval=0s timeout=240 (drbd-start-interval-0s)
               stop interval=0s timeout=100 (drbd-stop-interval-0s)
 Resource: metadata-fs (class=ocf provider=heartbeat type=Filesystem)
  Attributes: device=/dev/drbd/by-res/r0/0 directory=/var/lib/nfs_shared
fstype=ext4 options=noatime
  Operations: monitor interval=20 timeout=40
(metadata-fs-monitor-interval-20)
              start interval=0s timeout=60 (metadata-fs-start-interval-0s)
              stop interval=0s timeout=60 (metadata-fs-stop-interval-0s)

Location Constraints:
Ordering Constraints:
  promote drbd-clone then start metadata-fs (kind:Mandatory)
Colocation Constraints:
  metadata-fs with drbd-clone (score:INFINITY) (with-rsc-role:Master)

Shouldn't one of the clones be promoted to the Master state automatically?

Regards,
  Dennis




More information about the Users mailing list