sillsdev / sillsdev/languageforge-lexbox
Kopia backup jobs should be killed if they run too long
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
Describe the bug
A current issue in k8s is causing kopia-backup jobs to stall/take forever.
As a result, the previous cron-job is still running when a new one is started.
The new one fails with Containers with incomplete status: [postgres-dump] presumably, because there's already a job running.
That's just confusing noise.
We should probably just kill a job if it takes longer than X (12?) hours.
We'll still get loads of alerts, because we're alerted if a job takes longer than 1h to complete.
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 locating the Kubernetes configuration for the kopia-backup CronJob and inspect how its job timeout and overlapping runs are controlled. Confirm the change by ensuring a stalled job is terminated after the chosen limit and that a later scheduled run is not blocked by the previous one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100