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

Safe cut over #64

Merged
merged 6 commits into from
Jun 15, 2016
Merged

Safe cut over #64

merged 6 commits into from
Jun 15, 2016

Conversation

shlomi-noach
Copy link
Contributor

  • Supporting multi-step, safe cut-over phase, where queries are blocked throughout the phase, and worst case scenario is table outage (no data corruption)
  • Self-rollsback in case of failure (restored original table)

Shlomi Noach added 5 commits June 13, 2016 18:36
- Supporting multi-step, safe cut-over phase, where queries are blocked throughout the phase, and worst case scenario is table outage (no data corruption)
- Self-rollsback in case of failure (restored original table)
- Removed `CutOverVoluntaryLock` and associated code
- Removed `CutOverUdfWait`
- `RenameTablesRollback()` first attempts an atomic swap
- Removed `CutOverVoluntaryLock` and associated code
- Removed `CutOverUdfWait`
- `RenameTablesRollback()` first attempts an atomic swap
@shlomi-noach
Copy link
Contributor Author

Algorithm depicted in: #65

@shlomi-noach
Copy link
Contributor Author

Merging this under the assumption the algorithm is correct (right now a few hundred production tests show no error). Will revisit if need be.

@shlomi-noach shlomi-noach merged commit 574c372 into master Jun 15, 2016
@shlomi-noach shlomi-noach deleted the safe-cut-over branch June 15, 2016 08:14
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 this pull request may close these issues.

1 participant