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.

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

Recovery manager #96

Open
iakkus opened this issue Nov 6, 2020 · 0 comments
Open

Recovery manager #96

iakkus opened this issue Nov 6, 2020 · 0 comments
Labels
design The issue is related to the high-level architecture env/all To indicate something that applies to all environments feature_request New feature request help wanted Extra attention is needed

Comments

@iakkus
Copy link
Member

iakkus commented Nov 6, 2020

When functions execute, they create backups of the output they produce (i.e., the input(s) to the next function(s)) when they are finished executing (i.e., checkpointing). These backups should be used by a recovery manager in case of a failure of a subsequent function.

There should be some coordination with the recovery manager regarding when functions start, finish and fail.

See #85 for how these checkpoints are created and can be found.
@iakkus iakkus added feature_request New feature request design The issue is related to the high-level architecture env/all To indicate something that applies to all environments help wanted Extra attention is needed labels Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design The issue is related to the high-level architecture env/all To indicate something that applies to all environments feature_request New feature request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iakkus