Handle elasticsearch becoming read only due to low disk space
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
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];'}}}```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ElasticSyncService path that logs indexing failures and inspect how Elasticsearch bulk responses are handled. Reproduce the read-only 429 condition if possible, then verify that failed indexing is not silently ignored and that synchronization recovers after Elasticsearch becomes writable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, python
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100