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

Halting a workflow should purge its messages from RabbitMQ #25

Open

1fish2 opened this issue Dec 6, 2019 · 0 comments

Collaborator

1fish2 commented Dec 6, 2019

Halting a workflow should purge its messages from RabbitMQ so that existing and new Sisyphus workers won't retry any of its tasks until the user resumes the workflow.
If a worker acknowledges a purged message, that needs to react gracefully.
This fix might have to wait until each workflow has its own queue.

RabbitMQ is not part of the user model so users should not need to know how to administer it to recover from problems.

Users should be able to halt a workflow, delete any stuck workers (as in #24), then fix a bug and start new workers without them also getting stuck.

1fish2 mentioned this issue

Sisyphus gets stuck pulling an input file #24

Closed

1 task

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