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

Separate migration planning and execution #104

Open
fintelia opened this issue Sep 20, 2018 · 0 comments
Open

Separate migration planning and execution #104

fintelia opened this issue Sep 20, 2018 · 0 comments
Labels
enhancement New feature or request m-migrations Related to changes to the data-flow graph

Comments

@fintelia
Copy link
Member

Currently, the planning for a migration is interleaved with its actual execution. In addition to being unfortunate from a code cleanliness perspective, it also makes the code very hard to reason about with regards to fault tolerance. In fact, there are almost surely critical sections during which a failure could cause the entire system to deadlock.

@fintelia fintelia added enhancement New feature or request m-migrations Related to changes to the data-flow graph labels Sep 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request m-migrations Related to changes to the data-flow graph
Projects
None yet
Development

No branches or pull requests

1 participant