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

Mark a job as poisonous after n recoveries #35

Open
olttwa opened this issue Jun 9, 2022 · 0 comments
Open

Mark a job as poisonous after n recoveries #35

olttwa opened this issue Jun 9, 2022 · 0 comments
Labels

Comments

@olttwa
Copy link
Member

olttwa commented Jun 9, 2022

Sometimes, a job execution might lead to worker process being crashed.

Due to orphan-checks, such jobs will be re-enqueued & retried.

Keep a note of recovered jobs, if a job is recovered more than n times, it can be assumed it's poisonous & leads to worker crash.

@olttwa olttwa added the feature label Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant