If one job generates too many events, other jobs will also be affected
Open
Nobody has claimed this yet.
known issue
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
Currently, to prevent the event collection from affecting our core functions e.g. job submission, we set up the following disk size control strategy for event watcher:
- In event watcher, check the disk usage in the beginning. If the disk usage > 80%, stop the event watcher and exit with a non-zero code.
- The disk check also happens every 60s. If the disk usage > 80%, stop the event watcher and exit with a non-zero code.
60sand80%are configurable.
However, this simple strategy will bring the following problem:
- If a job generates too many events, it will affect all other jobs. To be detailed, other jobs' events will not be collected.
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
The issue names no file, test, or concrete entry point beyond the event watcher and its disk-usage checks. Start by locating the event watcher implementation and how it associates events with jobs. Define how excessive events from one job should be isolated without affecting other jobs, then add validation for the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100