orchestrator icon indicating copy to clipboard operation
orchestrator copied to clipboard

Issue/question with graceful-master-takeover finding 2 potential masters

Open egezonberisha opened this issue 4 years ago • 1 comments

Quick question. We have a setup CoMaster topology setup and a read node.

Topology example:

CoMasterA (read_write) <---replication flowing both ways----> CoMasterB(read_only)
      |
      |
ReplicaNode(read_only)

In the setup above, when I want to perform graceful-master-takeover I get:

$ orchestrator-client -c graceful-master-takeover -alias db-alias-1 -d CoMasterB
Cannot deduce cluster master for CoMasterA:3306. Found 2 potential masters

Which by design (according to documentation) makes sense, but shouldn't the orchestrator know which one is the actual master by looking at read_only variable? And only if the CoMasterA and CoMasterB are both read/write then say Found 2 potential masters, otherwise do the failover since there is only one node in read/write mode.

Thanks, -Egezon

egezonberisha avatar May 07 '21 22:05 egezonberisha

graceful-master-takeover was not designed for M-M topologies, but I see what you mean. Making this a feature request.

shlomi-noach avatar May 10 '21 04:05 shlomi-noach