-
Notifications
You must be signed in to change notification settings - Fork 168
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
We allow breaking of an existing co-master replication. Here's the breakdown: Ideally, this would not eb allowed, and we would first require the user to RESET SLAVE on 'master' prior to making it participate as co-master with our 'instance'. However there's the problem that upon RESET SLAVE we lose the replication's user/password info. Thus, we come up with the following rule: If S replicates from M1, and M1<->M2 are co masters, we allow S to become co-master of M1 (S<->M1) if: - M1 is writeable - M2 is read-only or is unreachable/invalid - S is read-only And so we will be replacing one read-only co-master with another. (instance_topology.go) supported by Web interface (cluster.js)
- Loading branch information
1 parent
6da558d
commit df7f7bb
Showing
4 changed files
with
50 additions
and
20 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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