Hi Karthick, (disclaimer: I am one of the authors of Replication Manager for MariaDB) you seem to be using outdated instructions. Please grab the 1.0.2 release for your distribution there: https://github.com/tanji/replication-manager/releases Replication Manager works best when used independently from MaxScale. Please read our documentation at https://github.com/tanji/replication-manager/blob/develop/README.md and let me know if you have any questions. Best Guillaume Le ven. 3 mars 2017 à 00:05, Karthick Subramanian < ksubramanian@paycommerce.com> a écrit :
Hi Experts,
I have a 2 db server with one as master and another one as slave.
Maxscale implemented with below monitor config:
*[MySQL Monitor]* *type=monitor* *module=mysqlmon* *servers=master1,slave1* *monitor_interval=500* *script=/usr/bin/replication-manager --user root:password --rpluser replusr:password * *--hosts $INITIATOR,$NODELIST --failover=force --interactive=false* *events=master_down*
When I shutdown master, failover is not automated. MRM (Replication Manager) is not promoting the slave to master automatically.
In maxscale log, I noticed below:
*2017-03-02 03:33:36 notice : Executed monitor script '/usr/bin/replication-manager --user root:password --rpluser replusr:password --hosts $INITIATOR,$NODELIST --failover=force --interactive=false' on event 'master_down'.* *2017-03-02 03:33:36 error : No Master can be determined.*
Is this because I didn't have the quorum (no slave) since its one master and one slave set-up. Is there any workaround.
Regards, Kart
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp