elasticsearch-HQ icon indicating copy to clipboard operation
elasticsearch-HQ copied to clipboard

If Cluster Status is Yellow or Red (i.e. recovering shards) elastichq is unable to function

Open thoro opened this issue 4 years ago • 0 comments

General information

  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Docker Container
  • ElasticHQ Version: 3.5.12
  • Elasticsearch Version: 6.7
  • Python version (ignore is using docker image):
  • Browser Vendor and Version (if applicable): Chrome

Issue Description

Whenever I access elastichq while the cluster status is red or yellow (i.e. recovering shards) it main page loads and then times out.

I checked the logs, apart from logging the raw data, it also shows timeout error after 30 sec on the following paths:

/_cluster/stats /_stats /_cat/nodes?format=json&full_id=true&h=id%2Cm%2Cn%2Cu%2Crole%2Chc%2Chm%2Chp%2Cip%2Cdt%2Cdu%2Cdisk.avail%2Cl

And the web endpoint then returns:

{ "message": "Oops! Something bad happened.", "status_code": 500 }

Is there an option to request the indices separatly, increase the timeout, or somehow otherwise handle it, so that at least the basic node management functions are available?

Source Code / Logs

Be Patient

I have a day job. ;-)

thoro avatar Feb 21 '20 07:02 thoro