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

RedisBroker: Track non-idempotent jobs as running, too #38

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

0xDEC0DE
Copy link
Contributor

Push running-job markers down into the Redis for all jobs, and move the logic for re-enqueueing jobs from dead brokers into the script itself. Non-idempotent jobs running on a dead broker are still NOT re-enqueued.

This should cause non-idempotent jobs to no longer run "invisibly" on a Redis broker, as well as causing dead brokers to signal any non-idempotent jobs that were running on them as failed.

Fixes: Issue #18

Push running-job markers down into the Redis for all jobs, and move
the logic for re-enqueueing jobs from dead brokers into the script
itself.  Non-idempotent jobs running on a dead broker are still NOT
re-enqueued.

This should cause non-idempotent jobs to no longer run "invisibly"
on a Redis broker, as well as causing dead brokers to signal any
non-idempotent jobs that were running on them as failed.

Fixes: Issue NicolasLM#18
@bigjools
Copy link
Collaborator

Got hit by this one today when that worker got killed!

@bigjools bigjools merged commit 3e4df65 into NicolasLM:master Mar 27, 2024
7 checks passed
@0xDEC0DE 0xDEC0DE deleted the issue/18 branch March 27, 2024 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants