Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle elasticsearch becoming read only due to low disk space #14

Open
jackrobison opened this issue Apr 2, 2022 · 0 comments
Open

Handle elasticsearch becoming read only due to low disk space #14

jackrobison opened this issue Apr 2, 2022 · 0 comments
Labels
area: elasticsearch consider soon Discuss this issue at the next planning meeting, then remove this label type: bug Existing functionality is wrong or broken

Comments

@jackrobison
Copy link
Member

The elastic sync service should handle ES temporarily becoming read only and recover when ES becomes writable, currently the failed queries are ignored:

2022-04-02 10:42:23,620 - scribe.service.ElasticSyncService - WARNING - indexing failed for an item: {'update': {'_index': 'claims', '_type': '_doc', '_id': '4023ca39b415cd916a304d71a3d528d8770f2ca5', 'status': 429, 'error': {'type': 'cluster_block_exception', 'reason': 'index [claims] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];'}}}
@jackrobison jackrobison added type: bug Existing functionality is wrong or broken area: elasticsearch consider soon Discuss this issue at the next planning meeting, then remove this label labels Apr 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: elasticsearch consider soon Discuss this issue at the next planning meeting, then remove this label type: bug Existing functionality is wrong or broken
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jackrobison