3079423 - HANA managed via Cluster Software causing traces like HANA_CALL timed out & Dual primary detected

The HANA DB is setup as High Availability Environment managed by a SUSE or Red Hat Cluster, usually via Pacemaker.

The cluster software did a health check and found "Dual primary detected" which caused a restart of the secondary database.

Trace:
Jul 16 04:04:52 SAPHana(SAPHana_E01_00)[19572]: WARNING: HANA_CALL timed out after 10 seconds running command 'HDB version'
Jul 16 04:04:52 SAPHana(SAPHana_E01_00)[19572]: INFO: RA ==== begin action monitor_clone (0.154.0) ====
Jul 16 04:04:52 SAPHana(SAPHana_E01_00)[19572]: INFO: RA: SRHOOK1=
Jul 16 04:04:52 SAPHana(SAPHana_E01_00)[19572]: INFO: RA: SRHOOK2=SOK
Jul 16 04:04:52 SAPHana(SAPHana_E01_00)[19572]: INFO: RA: SRHOOK3=SOK
Jul 16 04:05:52 SAPHana(SAPHana_E01_00)[19572]: WARNING: HANA_CALL timed out after 60 seconds running command 'hdbnsutil -sr_state'
Jul 16 04:05:52 SAPHana(SAPHana_E01_00)[19572]: ERROR: ACT: check_for_primary: we didn't expect node_status to be: <>
Jul 16 04:05:52 SAPHana(SAPHana_E01_00)[19572]: ERROR: ACT: check_for_primary: we didn't expect node_status to be: DUMP <00000000 0a |.|
Jul 16 04:06:54 SAPHana(SAPHana_E01_00)[19572]: WARNING: HANA_CALL timed out after 60 seconds running command 'hdbnsutil -sr_state'
Jul 16 04:06:54 SAPHana(SAPHana_E01_00)[19572]: ERROR: ACT: check_for_primary: we didn't expect node_status to be: <>
Jul 16 04:06:54 SAPHana(SAPHana_E01_00)[19572]: ERROR: ACT: check_for_primary: we didn't expect node_status to be: DUMP <00000000 0a |.|
Jul 16 04:07:56 SAPHana(SAPHana_E01_00)[19572]: WARNING: HANA_CALL timed out after 60 seconds running command 'hdbnsutil -sr_state'
Jul 16 04:07:56 SAPHana(SAPHana_E01_00)[19572]: ERROR: ACT: check_for_primary: we didn't expect node_status to be: <>
Jul 16 04:07:56 SAPHana(SAPHana_E01_00)[19572]: ERROR: ACT: check_for_primary: we didn't expect node_status to be: DUMP <00000000 0a |.|
Jul 16 04:08:30 SAPHana(SAPHana_E01_00)[19572]: INFO: ACT: Using getParameter.py as fallback - node_status=primary
Jul 16 04:08:50 SAPHana(SAPHana_E01_00)[19572]: INFO: RA: SRHOOK1=
Jul 16 04:08:50 SAPHana(SAPHana_E01_00)[19572]: INFO: RA: SRHOOK2=SOK
Jul 16 04:08:50 SAPHana(SAPHana_E01_00)[19572]: INFO: RA: SRHOOK3=SOK
Jul 16 04:08:50 SAPHana(SAPHana_E01_00)[19572]: INFO: DEC: Dual primary detected, other instance is PROMOTED and lpa stalemate ==> local restart
Jul 16 04:08:50 SAPHana(SAPHana_E01_00)[19572]: INFO: RA ==== end action monitor_clone with rc=7 (0.154.0) (249s)====

cluster replication ha pacemaker , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem