Verifying the Pacemaker configuration
- Log in to the primary node as root, or as a user with superuser privileges.
Check resource defaults.
pcs resource defaultsExample result:
Check property defaults.
pcs propertyExample result:
Cluster Properties: cluster-infrastructure: corosync cluster-name: serviced-ha dc-version: 1.1.12-a14efad have-watchdog: false no-quorum-policy: ignore stonith-enabled: false
Review the resource constraints.
The ordering constraint should show that serviced-group starts after DFSMaster (the DRBD master). The colocation constraint should show that serviced-group resource and DFSMaster are on the same active cluster node.
pcs constraintExample result:
Location Constraints: Ordering Constraints: promote DFSMaster then start serviced-group (kind:Mandatory) Colocation Constraints: serviced-group with DFSMaster (score:INFINITY) (with-rsc-role:Master)
Review the ordering of the serviced-group resource group.
pcs resource show --full
The resources in a resource group are started in the order they appear in the group, and stopped in the reverse order they appear in the group. The correct start order is: