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.

Sign up for GitHub

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

Jump to bottom

Mark a job as poisonous after n recoveries #35

Open

olttwa opened this issue Jun 9, 2022 · 0 comments

Labels

feature

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 added this to Goose 0.3.0

olttwa moved this to Todo in Goose 0.3.0

olttwa removed this from Goose 0.3.0

olttwa added the feature label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment