Open thoro opened 4 years ago
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?
I have a day job. ;-)
General information
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. ;-)