Question: why are master/master configs unsupported?
Open
question
- Dominant language
- Go
- Stars
- 13.6k
- Forks
- 1.4k
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 4
Description
The tool bails out if a master-master pair is detected anywhere in the replication hierarchy (even if it's in a different branch), but I'm not actually sure why? I can see why it might cause issues with `--test-on-replica` (if the replica were a member of the master/master pair), but are there any other issues to be aware of? Given a topology like the following:
Is there any danger running `gh-ost` pointed to one of R1/R2/R3?
Contributor guide
Assessment
This issue has not been assessed yet.