You must restart the standby pods after a node is shut down. Restarting the standby pods distributes the Avaya Analytics™ standby pods across three nodes instead of two for efficient load balancing of the Avaya Analytics™ pods.
Note:
This procedure is only applicable to Avaya Analytics™ High Availability (HA) deployments.
Before you begin
Check the status of the HA pods.
Log in to the Cluster Control Manager (CCM) console as a 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 General by pressing the corresponding number.
To restart the standby pods, select the Restart Standby Pods option by entering the corresponding number.
In the Proceed to Standby pods restart? option, enter y.
ADDITIONAL INFORMATION:
This step checks the logs of the standby pods for their HA status and displays a list of the standby pods or the services that the script restarts.
In the Are you sure you want to restart the services listed above? option, enter y.
STEP RESULT:
This step restarts all the services in a sequential order. After the completion of the process, CCM console displays DONE.
Return to the previous page by entering b.
Quit the current page by entering q.
Return to the main menu by entering m.
To check the status of all pods, in the CCM console, run the following command:
ADDITIONAL INFORMATION:
kubectl get pods | grep orca
Ensure that the STATUS column of the pods displays Running and READY column displays 1/1.
To monitor the pods that you have restarted, run the following command:
