Restarting measure processors

Last Updated : Jun 24, 2021 |
Prolog information
Metadata
Keywords:
In Avaya Analytics™, on the completion of an engagement, the engagement gets added to the database. An engagement can have multiple events. When an event occurs, measures get incremental, which creates the following differences:
  • The count of selected measures does not match the number of items when you drill-down in a report.
  • If the engagement is still in process for a measure, the browser displays a No Results warning.
To resolve this issue, you must restart the measure processors, the Reliable Eventing Framework (REF) input adaptor, and the interval controller. The restart process also ensures efficient load balancing of the pods.
Other:
You must restart the measure processors only during a maintenance window.
  1. Log in to the Cluster Control Manager (CCM) console as a cust user.
  2. Switch to being the root user by entering the command su.
  3. To run the Analytics Administration script, use the following command:
    ADDITIONAL INFORMATION:
    ccm release orca analytics
  4. Select Troubleshooting by pressing the corresponding number.
  5. Select General by pressing the corresponding number.
  6. To restart the measure processors, select the Restart Measure Processors option by entering the corresponding number.
  7. In the Proceed to Measure Processing Pods restart option, type y.
    STEP RESULT:
    CCM console displays the following list of services that restart after you confirm to proceed:
    • The measure processors
    • The REF input adaptor
    • The interval controller
  8. In the Are you sure you wish to continue? option, enter y.
    ADDITIONAL INFORMATION:
    Note:
    This step resets the real-time data.
    STEP RESULT:
    This step restarts all the services in a sequential order. After the completion of the process, CCM console displays the message as DONE.
  9. Return to the previous page by entering b.
  10. Quit the current page by entering q.
  11. Return to the main menu by entering m.
  12. To check the status of all pods, in the CCM console, run the following command as a customer user:
    ADDITIONAL INFORMATION:
    kubectl get pods | grep orca
    STEP RESULT:
    The services that you restarted displays the STATUS column as Running and the READY column as 0/1.
  13. Wait for the READY column to display 1/1.
  14. To monitor the readiness of the pods that you restarted, run the following command:
    ADDITIONAL INFORMATION:
    kubectl get pods -w | grep orca
    ADDITIONAL INFORMATION:
    The services take about 15 minutes to restart. If the services do not restart after 15 mins, contact Avaya support.
  15. Return to the previous page by entering b.
  16. Quit the current page by entering q.
  17. Return to the main menu by entering m.