Orchestrator Integration#1626
Merged
Merged
Conversation
Contributor
|
LGTM |
enisoc
force-pushed
the
orchestrator
branch
2 times, most recently
from
f150afa to
7157b9b
Compare
enisoc
force-pushed
the
orchestrator
branch
3 times, most recently
from
ae7084f to
3397cbc
Compare
Contributor
Author
|
@alainjobart PTAL. The main integration features are there now. What's left is to write documentation, and incorporate it into the local example as well. I can do that after the code freeze. |
Contributor
|
|
added 6 commits
June 6, 2016 14:16
This can be used to propagate Vitess identity info to tools that work at the MySQL level.
For now, it is a single instance. Later, I plan to connect multiple nodes, each containing its own Orchestrator+Galera.
This clears out the connection parameters in addition to the replication position.
If a tablet finishes restoring and finds that it's supposed to be the master, it should not try to replicate from itself. Instead, we'll wait for the operator to elect a new master, because it's not clear how we ended up in this situation.
This prevents the operator from having to manually tell Orchestrator to discover new shards. It also makes a number of scenarios self-healing -- for example, if the Orchestrator backing database is lost, it will automatically repopulate over time.
When Vitess stops replication on purpose (e.g. for vtworker batch processes), we now take a maintenance lock on it. This tells Orchestrator not to reparent the instance or restart replication on it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change is