Use this procedure to check the status of replication between primary and replica pods on DC1 and between DC1 and DC2.
Log in to the Cluster Control Manager (CCM) console as the customer user.
Switch to being the root user by entering the command su.
To run the Analytics Administration script, use the following command:
ADDITIONAL INFORMATION:
ccm release orca analytics
Select Troubleshooting by pressing the corresponding number.
Select Database by pressing the corresponding number.
To check Crunchy pod replication status, enter the corresponding number.
STEP RESULT:
The output from the script shows different information for each pod depending on whether a pod is a primary, a standby replica, or a Geo replica. The expectations are as follows:
The primary pod crunchy-primary-service-orca-dbmgr-0 must be listed as master list of replicas.
The master list displays a list of replica pods listening to the primary pod.
