Go error during failover: slice bounds out of range about replication-manager HOT 7 CLOSED

Hi,

Yes, I can see the problem, although I am not sure why it occurs - I have never encountered this issue myself. I will release a fix.

For MaxScale, yes, it is indeed a problem - I will talk to the MaxScale team about this.

Thanks for reporting!

from replication-manager.

Thanks!
For now I prepended the hosts with the $initiator and this should work in theory.

from replication-manager.

Just pulled the latest version, compiled it and it works now:
sudo /usr/local/bin/replication-manager --user=root:toor --rpluser=repl:repl --hosts=10.10.18.11:3306,10.10.18.12:3306,10.10.18.13:3306 --failover=force --interactive=false --logfile=/var/log/failover.log
2016/03/16 14:43:05 INFO : Server 10.10.18.11:3306 is dead.
2016/03/16 14:43:05 INFO : Starting master switch
2016/03/16 14:43:05 INFO : Electing a new master

Thanks! 👍

from replication-manager.

Ran into the same problem. Can we have a new release for this @tanji?

thanks and cheers

from replication-manager.

@tanji just saw there is already one. You are too fast for me. :-)

from replication-manager.

@banpei-dbart I heard from the MaxScale Team that this change of behavior was wanted, so I have to update my failover instructions as well, it seems... sorry for that.

from replication-manager.

No problem. Thanks for asking them! :)

from replication-manager.