Too many job history records will affect core functions like job submission
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, all job records history (e.g. framework retry history, task deletuib history) will be recorded into db without any control.
If one job has too many job history records, the database size will run out, which wil affect our core functions e.g. job submission.
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 files or tests. Start by tracing where framework retry and task deletion histories are persisted and how job submission interacts with the database. Define the retention or control behavior and verify that history growth is bounded without breaking job submission.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100