Error when splitting GTID when failing over about replication-manager HOT 14 CLOSED

I guess this is due to mrm not supporting multiple domains?

from replication-manager.

Not supported at this time, but this is a priority goal for 0.7

from replication-manager.

Hello Tanji,

I am facing error splitting GTID issue with 0.7 dev release also.

[root@maxscale ~]# replication-manager --hosts=mariadb1:3306,mariadb2:3306,mariadb3:3306 --user=root:root123 --rpluser=admin:mariadb failover --logfile=/var/log/mrm.log --verbose
2016/06/20 15:31:37 DEBUG: Creating new server: mariadb1:3306
2016/06/20 15:31:37 DEBUG: Checking if server mariadb1:3306 is slave
2016/06/20 15:31:37 DEBUG: Server mariadb1:3306 is not a slave. Setting aside
2016/06/20 15:31:37 DEBUG: Creating new server: mariadb2:3306
2016/06/20 15:31:37 DEBUG: Checking if server mariadb2:3306 is slave
2016/06/20 15:31:37 DEBUG: Server mariadb2:3306 is configured as a slave
2016/06/20 15:31:37 DEBUG: Creating new server: mariadb3:3306
2016/06/20 15:31:37 DEBUG: Checking if server mariadb3:3306 is slave
2016/06/20 15:31:37 DEBUG: Server mariadb3:3306 is configured as a slave
2016/06/20 15:31:37 DEBUG: Server mariadb1:3306 was autodetected as a master
2016/06/20 15:31:37 DEBUG: Checking if server mariadb2 is a slave of server mariadb1
2016/06/20 15:31:37 DEBUG: Checking if server mariadb3 is a slave of server mariadb1
2016/06/20 15:31:37 DEBUG: Server [0] mariadb1:3306 Master
2016/06/20 15:31:37 DEBUG: Server [1] mariadb2:3306 Slave
2016/06/20 15:31:37 DEBUG: Server [2] mariadb3:3306 Slave
2016/06/20 15:31:37 INFO : Starting master switch
2016/06/20 15:31:37 INFO : Electing a new master
2016/06/20 15:31:37 DEBUG: Processing 2 candidates
2016/06/20 15:31:37 DEBUG: Checking eligibility of slave server mariadb2:3306 [0]
2016/06/20 15:31:37 Error splitting GTID: 0-3-347,1-1-17

Please help

from replication-manager.

hi @singhdilip13 this is work in progress. It should be released in a couple of days. I'll keep you posted. Thanks for your interest in MRM

from replication-manager.

Closed by commit ca4cb55

from replication-manager.

Hello Tanji,

By when can we expect the new release because we need to implement this as earlier as possible.

from replication-manager.

@singhdilip13 the release is expected for October, but you can checkout the 0.7 code and build it.

from replication-manager.

Can you help me to generate executable binary from source code. Also the source code available for version 0.7 have that GTID fix??

from replication-manager.

sure thing, I'll do a beta release for you. just hang on for a while.

from replication-manager.

Check out https://github.com/mariadb-corporation/replication-manager/releases/tag/0.7.0-beta3

from replication-manager.

Thanks for the link.
One more thing in Master-Slave-Slave setup if master goes down then new_master is elected.
Now if slave is getting down i see error in mariadb log file saying that lost_master and vice versa in case of master failure it say lost_slave

from replication-manager.

It seems that you are talking about MaxScale, not MariaDB; Am I right?

from replication-manager.

Yes maxscale my mistake

from replication-manager.

In this case I don't know about it, sorry. Are you using latest MaxScale 1.4.3?

from replication-manager.