Job lease attempt high water marks
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
An aggregation or collection job might get leased multiple times before it eventually succeeds. But the lease_attempt column gets reset to 0 on success. This can be frustrating if, after the fact, we want to see whether a job needed retries (perhaps to explain why it took so long).
I don't recall exactly why we reset the lease count, but if we can't change that, then maybe there's some other way we could track how many times the lease was acquired.
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 by tracing how aggregation and collection jobs acquire leases and where the lease_attempt column is reset on success. Determine whether the existing count can be preserved or whether a separate high-water mark is needed; done means successful jobs still expose how many lease attempts they required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100