Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: stuck SIGTERM #51

Merged
merged 4 commits into from
Jun 6, 2022
Merged

fix: stuck SIGTERM #51

merged 4 commits into from
Jun 6, 2022

Conversation

patrykcieszkowski
Copy link
Contributor

@patrykcieszkowski patrykcieszkowski commented May 30, 2022

  • don't index job until the ack response is received
  • remove jobs from the index after 30s timeout
  • make sure failed jobs are removed from the index
  • SIGTERM timeout - 60s

@jimaek
Copy link
Member

jimaek commented May 30, 2022

We should also maybe make the health reboot able to force kill everything after a timeout. To have a plan b available to us. That way we only have to wait 7 days to get stuck probes instead of months

@patrykcieszkowski patrykcieszkowski changed the title fix: job count fix: stuck SIGTERM May 31, 2022
@jimaek jimaek requested a review from zarianec May 31, 2022 17:35
@jimaek jimaek linked an issue May 31, 2022 that may be closed by this pull request
@jimaek jimaek merged commit 46449c2 into master Jun 6, 2022
@jimaek jimaek deleted the job-count-ack branch June 6, 2022 18:32
@github-actions
Copy link

github-actions bot commented Jun 6, 2022

🎉 This PR is included in version 0.5.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Probes dont always update
2 participants