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

WIP Idea: Add checkpointing to continue requests after failures #17

Open
devslash-paul opened this issue Jul 3, 2019 · 0 comments · May be fixed by #31
Open

WIP Idea: Add checkpointing to continue requests after failures #17

devslash-paul opened this issue Jul 3, 2019 · 0 comments · May be fixed by #31

Comments

@devslash-paul
Copy link
Owner

When something fails - eg an internet outage, it's super annoying to have to restart the entire set of requests. It would be useful instead if there was some form of checkpointing.

Thinking of

runHttp {
  call('...') {
     data = Checkpoint(FileDataSupplier(...))
  }
}

The checkpoint will work via using a file based at a {cwd}/.fetchDSL folder. Each invocation can be named, or otherwise a 'global' checkpoint will be used in which case it's unsafe to run multiple checkpoints at the same time.

The easiest way to do checkpointing will be adding metadata to a envelope that encapsulates the request. This context object will be able to be received later to identify when a request has made it through the pipeline and can be marked as successful.

Another requirement is deterministic ordering of the input if checkpointing needs index based skips. Given that the concurrent nature of the produceHttp section is largely to handle the case of slow before sections, this should be fine. Though it would potentially lose the ability to use a slow (but thread safe) data provider.

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 a pull request may close this issue.

1 participant