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

Task action: "Suspend after next checkpoint" #4748

Open
pataquets opened this issue May 18, 2022 · 0 comments
Open

Task action: "Suspend after next checkpoint" #4748

pataquets opened this issue May 18, 2022 · 0 comments

Comments

@pataquets
Copy link

pataquets commented May 18, 2022

Describe the problem
On client shutdown or task suspend, non-checkpointed work is lost. So far, I've found uncheckpointed work for 1h or even 2h worth, which is quite a waste, if stopped and lost.
When an orderly shutdown is possible (eg. reviewing tasks before shutdown/restart), you can wait tasks to checkpoint before suspending/quitting, but it's tedious and inconvenient.
It can be helpful when shutting down, but also for switching tasks/projects.

Describe the solution you'd like
I would like to have a 'Suspend after next checkpoint' task action. Thus, I could send it to all running tasks to guarantee that no work is lost.

Additional context
Assumptions:

  • Tasks notify client on checkpoint, which can react accordingly.
  • Some tasks do not checkpoint, which is fine. It's up to you to know it if you intend to do "whatever at checkpoint".

This feature would later enable also a 'checkpointed shutdown' for the whole client. You can manually trigger it as a command when winding down before shutdown, set it as an opt-in behaviour on SIGTERM or do it on another signal. Lots of people might find it helpful to avoid wasted work (time and electricity).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants