Crash enqueue replication server process - SAP NetWeaver on Amazon
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Crash enqueue replication server process

Description – crash enqueue replication server process using kill.

Run node – secondary node where ERS is running.

Run steps

[root@hahost02 ~]# ps -ef | grep enqr
ha1adm    201662  201652  2 17:28 ?        00:00:01 enqr.sap1_ERS10 pf=/usr/sap/HA1/SYS/profile/HA1_ERS10_ershost
root      202061  201009  0 17:29 pts/0    00:00:00 grep --color=auto enqr
[root@hahost02 ~]# kill -9 201662

Expected result – ERS will restart on the same node, and no action is taken by the cluster.

[root@hahost02 ~]# pcs status
Cluster name: rhelha
Stack: corosync
Current DC: hahost02 (version 1.1.19-8.el7_6.5-c3c624ea3d) - partition with quorum
Last updated: Wed May 12 18:20:57 2021
Last change: Wed May 12 17:29:51 2021 by root via crm_resource on hahost02

2 nodes configured
7 resources configured

Online: [ hahost01 hahost02 ]

Full list of resources:
 
 clusterfence   (stonith:fence_aws):    Started hahost02
 Resource Group: HA1_ASCS00_group
     rsc_fs_ascs00     (ocf::heartbeat:Filesystem):    Started hahost01  
     rsc_vip_ascs00    (ocf::heartbeat:aws-vpc-move-ip):       Started hahost01
     rsc_ascs00       (ocf::heartbeat:SAPInstance):   Started hahost01
 Resource Group: HA1_ERS10_group
     rsc_fs_ers10      (ocf::heartbeat:Filesystem):    Started hahost02
     rsc_vip_ers10      (ocf::heartbeat:aws-vpc-move-ip):       Started hahost02
     rsc_ers10  (ocf::heartbeat:SAPInstance):   Started hahost02

Failed Actions:
* rsc_ers10_monitor_120000 on hahost02 'not running' (7): call=87, status=complete, exitreason='',
    last-rc-change='Wed May 12 17:30:52 2021', queued=0ms, exec=0ms


Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled

Recovery procedure – N/A.