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

Don't change task states upon restart #117

Closed
dpmatthews opened this issue Sep 13, 2012 · 1 comment
Closed

Don't change task states upon restart #117

dpmatthews opened this issue Sep 13, 2012 · 1 comment
Assignees

Comments

@dpmatthews
Copy link
Contributor

The default action when performing a restart should be to start the suite in exactly the same state defined in the restart file. This is the safest behaviour, is the least likely to surprise the user and is necessary if we want cylc to be able update the status of tasks upon restart (see #86). However, this is not the behaviour at present. Even using the options --no-reset and --no-release you still end up with, for instance, any tasks which were in the submitted or running states being re-run.

@cylc
Copy link
Collaborator

cylc commented Sep 13, 2012

Current behaviour was intended to save the operator, potentially, from a lot of manual triggering - imagine loadleveler going down just after a large ensemble is submitted by cylc - and it is "safe" in the sense that it assumes the worst (any task that was not finished at shutdown must be re-run) and if a failed task was not fixed it will just fail again so we're no worse off.

That said, your solution provides the ultimate safety and avoids unnecessary re-runs, and we could keep the current behaviour as an option (e.g. 'cylc restart --trigger-all') and/or provide run time controls to re-trigger multiple tasks at once. In other words, I agree.

@ghost ghost assigned hjoliver Oct 5, 2012
hjoliver added a commit to hjoliver/cylc-flow that referenced this issue Nov 30, 2012
hjoliver added a commit that referenced this issue Dec 3, 2012
Removed automatic task state alteration on restart (Issue #117).
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

No branches or pull requests

2 participants