Printer FriendlyEmail Article Link

Velocity: How to resolve Elastic Search Cluster is not operational issue on iTE?

Objective/Summary

This article describes how to resolve ‘Elastic Search Cluster is not operational’ issue on iTE
 

Environment/Versions
Spirent Velocity & iTE
Procedure
If several errors (Unsuccessful HTTP, DBs not initialized or An unexpected error has occured. Please contact your administrator to check the system) are displayed on Velocity UI and ITE UI shows an error that Elastic Search Cluster is not operational, perform these steps:
  • On iTE VM, go to folder /data/logs/esearch-output.log
  • Check for java exceptions which reference an .es_temp_file
  • If there are such exceptions then stop the Elasticsearch process if it's not stopped already by running command:  /local/rc-stop/esearch
  • Remove the referenced file temporary file
  • Restart iTE or just Elasticsearch using command: /local/rc-start/esearch
Notes
This is a known issue with Elasticsearch: https://github.com/elastic/elasticsearch/pull/21210. It is fixed in Elastic 5.6.0

Product : Velocity