An SAPHana resource doesn't promote at cluster startup after rebooting both nodes in a Pacemaker cluster
Issue
- An
ocf:heartbeat:SAPHana
resource is scheduled to promote on node 1 when the cluster starts, but then the master score is set to-1
, and Pacemaker tries to promote the resource on another node instead. - An
SAPHana
resource has its master score set to-1
during its start operation. - An
SAPHanaTopology
resource does not complete its first monitor operation before theSAPHana
resource sets the master score. - An
SAPHana
resource has startup issues after placing the cluster in maintenance mode, rebooting one or more nodes, possibly starting HANA System Replication manually, and taking the cluster out of maintenance mode. - A scenario like the one below occurred.
# Maintenance mode is unset
# Both nodes were rebooted while maintenance mode was in place
Aug 02 12:57:14 [137083] sapha033 crmd: info: abort_transition_graph: Transition aborted by cib-bootstrap-options-maintenance-mode doing modify maintenance-mode=false: Configuration change | cib=0.31.0 source=te_update_diff_v2:511 path=/cib/configuration/crm_config/cluster_property_set[@id='cib-bootstrap-options']/nvpair[@id='cib-bootstrap-options-maintenance-mode'] complete=true
# The SAPHanaTopology and SAPHana resources are currently stopped
Aug 02 12:57:15 [137082] sapha033 pengine: info: clone_print: Clone Set: TopologyA4P-clone [TopologyA4P]
Aug 02 12:57:15 [137082] sapha033 pengine: info: short_print: Stopped: [ sapha033hb0 sapha034hb0 ]
Aug 02 12:57:15 [137082] sapha033 pengine: info: clone_print: Master/Slave Set: MasterSlaveA4P [SAPHanaA4P]
Aug 02 12:57:15 [137082] sapha033 pengine: info: short_print: Stopped: [ sapha033hb0 sapha034hb0 ]
# The SAPHana resource is scheduled to be promoted on node 1
Aug 02 12:57:15 [137082] sapha033 pengine: notice: LogAction: * Promote SAPHanaA4P:0 ( Stopped -> Master sapha033hb0 )
# The SAPHanaTopology resource starts on node 1
Aug 02 12:57:20 SAPHanaTopology(TopologyA4P)[219870]: INFO: RA ==== begin action start_clone (0.152.22) ====
Aug 02 12:57:21 SAPHanaTopology(TopologyA4P)[219870]: INFO: RA ==== end action start_clone with rc=0 (0.152.22) (6s)====
# The SAPHana resource begins starting on node 1
Aug 02 12:57:22 SAPHana(SAPHanaA4P)[220613]: INFO: RA ==== begin action start_clone (0.152.21) ====
# The SAPHanaTopology resource begins its first monitor on node 1
Aug 02 12:57:26 SAPHanaTopology(TopologyA4P)[220612]: INFO: RA ==== begin action monitor_clone (0.152.22) ====
# The SAPHana resource sets the master score to -1 on node 1 and finishes its start operation
Aug 02 12:57:26 [137081] sapha033 attrd: info: attrd_peer_update: Setting master-SAPHanaA4P[sapha033hb0]: 5 -> -1 from sapha033hb0
...
Aug 02 12:57:26 SAPHana(SAPHanaA4P)[220613]: INFO: RA ==== end action start_clone with rc=0 (0.152.21) (5s)====
# The SAPHanaTopology resource sets the hana_<sid>_roles attribute
Aug 02 12:57:28 [137081] sapha033 attrd: info: attrd_peer_update: Setting hana_a4p_roles[sapha033hb0]: (null) -> 4:P:master1:master:worker:master from sapha033hb0
Environment
- Red Hat Enterprise Linux 7 for SAP Solutions
- Red Hat Enterprise Linux 8 for SAP Solutions
- Automated SAP HANA System Replication in Scale-Up in pacemaker cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.