[ES] Do not evaluate a deleted dataset
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
If for any reason a dataset is causing troubling to workers, it can be deleted. However, ES continues to send to workers the operations (referring to the incriminated dataset) already in the queue.
As they cannot be evaluated, such operations stay in the queue indefinitely.
This issue should probably be accounted with the new proposal for ES.
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
No files or tests are identified. Start by locating the ES queue and dataset evaluation path, then review the new ES proposal mentioned in the issue. Done means queued operations for deleted datasets no longer remain unevaluated indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100