Add functionality to purge periodic task execution histories
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 95
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 1
Description
https://github.com/closeio/tasktiger/issues/137 addresses purging tasks in an error state. But long running periodic tasks can have an ever increasing list of execution errors that will never get purged. A function should be provided that can be used to trim the execution list for periodic tasks so that they don't have unbounded growth.
Another idea would be to have a max executions config setting and do a LTRIM every time we add to the execution list here:
https://github.com/closeio/tasktiger/blob/fe82e842f42b28c46c265f4b54de0f776f776404/tasktiger/worker.py#L409-L412
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 in tasktiger/worker.py around lines 409-412 and review issue 137 for the existing purge behavior. Determine whether the periodic execution list should be trimmed through a purge function or a maximum-executions setting, using Redis LTRIM as referenced. Done means periodic task execution histories no longer grow without bound.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, redis
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100