You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While debugging and supporting users I have noted that a lack of disk space results in the error: elasticsearch.exceptions.TransportError: TransportError(429, 'cluster_block_exception', 'index [stations] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];')
which is raised inside the wis2box-api container.
This issue often goes unnoticed as the status of the wis2box-containers does not change and the error is not displayed in the Grafana Dashboard.
We should display this issue in the main Grafana dashboard and document it in the FAQ
The text was updated successfully, but these errors were encountered:
wis2box silently failing due the disk usage issue resulted in 5 days of data loss in the CMO-server, so I'm raising the priority of this issue.
I think instead of just displaying the disk usage issue we should consider disabling the wis2box as a whole when we detect that Elasticsearch stops functioning.
While debugging and supporting users I have noted that a lack of disk space results in the error:
elasticsearch.exceptions.TransportError: TransportError(429, 'cluster_block_exception', 'index [stations] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];')
which is raised inside the wis2box-api container.
This issue often goes unnoticed as the status of the wis2box-containers does not change and the error is not displayed in the Grafana Dashboard.
We should display this issue in the main Grafana dashboard and document it in the FAQ
The text was updated successfully, but these errors were encountered: