-
Notifications
You must be signed in to change notification settings - Fork 168
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
GET ERROR: Moving source lab_to_dr with empty password to preserve replication stream on new master #699
Comments
Yes it does as long as you declare your 2 clusters , each cluster it's source name and domain id add cluster-head = "cluster-haproxy-source1"
|
Just we have not been able to make such topology work with replication filters so far |
Hi @svaroqui Alternatively, is it possible to prevent slave02 from executing 'change master to channel lab_to_dr' when master02 failed? It's just like:
thanks for your reply. |
multi source replication does not work the way you describe it. We should no build on unsafe topology , just consider one cluster channel01 made with master01<-slave01 and <-master02 on domain 01, and an other cluster channel02 master02 <- slave02 on domain 02, if this not mariadb please consider 8.3 the new tagged GTID , ( but we do not yet support tags ) |
I think you could try not to name the source of the parent cluster and so the replication that glue the 2 clusters only naming the cluster02 |
Could you tag the issue with mysql or mariadb ? |
I guess that we could fixe it as i already notice this issue |
Hi @svaroqui I tried the above solution
But when master02 failed,slave02 is selected as master, but I still get the error When master02 recovers, it will not become a slave of slave02. I also hope that this problem will be solved. |
The problem is not about moving sources. your replication-manager clearly stated mysqlbinlog to rejoin using binary log. You have to specify using other method if you're not using binary logs to rejoin or specify your mysqlbinlog path installation |
Under the same parameter file, When using both Thank you for your reply. |
Can you provide us with the version your are using please also send your configs and logs in plain text, we have multiple paying user using that topology an not only for migration , but things have do be done correctly for that to work |
I have two clusters in repman
Master02 also acts as a slave to Master01 (using replication source lab_to_dr).
However, when Master02 failed, I received an error message indicating that Slave02 entered an empty password during the 'change master' process.
I was wondering replication manager supports this kind of architecture?
I'm happy to provide more information if needed.
The text was updated successfully, but these errors were encountered: