An SAPHana resource returns the wrong primary status for a node when the hdbnsutil -sr_state command doesn't respond

Solution In Progress - Updated -

Issue

  • A message like the following is logged, where node_status does not match the node's true current status, and then Pacemaker initiates a failover.

    ACT: Using getParameter.py as fallback - node_status=<wrong_status>
    
  • Secondary node does not get promoted after SAP HANA binaries are lost on the primary node in a High Availability cluster

  • HANA is in stopped state on both nodes of a Pacemaker cluster after losing the hdb binaries on the primary node.
  • When the cluster is in maintenance mode, HANA continues to run on both nodes after the hdb binaries are removed from one node. When the cluster is not in maintenance mode, the SAPHana resource agent takes action to stop the HANA instances.
  • The HANA instances are stopped and the following was logged:

    Apr  7 14:53:45 azr-eus2l1286 SAPHanaTopology(SAPHanaTopology_HNS_10)[119675]: ERROR: ACT: check_for_primary:  we didn't expect srmode to be: DUMP: <00000000  0a      |.|#01200000001>
    

Environment

  • Red Hat Enterprise Linux 6, 7, or 8 (with the High Availability Add-on)
  • SAP HANA System Replication in Scale-Up with Pacemaker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In