Concurrency issue in elastic search
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
Elastic search sometimes fails stochastically with the error:
{"error":{"root_cause":[{"type":"version_conflict_engine_exception","reason":"[data][125]: version conflict, required seqNo [108522], primary term [1]. current document has seqNo [108523] and primary term [1]","index_uuid":"d_zNAG--SW-U97P61jOrSg","shard":"0","index":"data"}],"type":"version_conflict_engine_exception","reason":"[data][125]: version conflict, required seqNo [108522], primary term [1]. current document has seqNo [108523] and primary term [1]","index_uuid":"d_zNAG--SW-U97P61jOrSg","shard":"0","index":"data"},"status":409}
on calling https://test.openml.org/api/v1/xml/data/untag
According to @joaquinvanschoren this is due to https://stackoverflow.com/questions/64034453/elastic-search-version-conflict-issue
Contributor guide
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 by reproducing the stochastic failure while calling https://test.openml.org/api/v1/xml/data/untag, then read the Elasticsearch version-conflict reference linked in the issue. Trace the endpoint's implementation and determine how concurrent updates produce the 409 response; done means the endpoint no longer fails with this conflict under the affected conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- api, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100