maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #04354
Re: Replication-manager + Maxscale
Hi Karthick,
Please also use the upcoming release 1.1 with is the current dev release on github
This is the best way to make this setup running
I ‘ll send you a package
if you tell me for what os ?
/stephane
Stéphane Varoqui, Senior Consultant
Phone: +33 695-926-401, skype: svaroqui
http://www.mariadb.com <http://www.mariadb.com/>
> Le 2 mars 2017 à 17:26, Guillaume Lefranc <guillaume@xxxxxxxxxxxx> a écrit :
>
> 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 <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 <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@xxxxxxxxxxxxxxx <mailto:ksubramanian@xxxxxxxxxxxxxxx>> 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 <https://launchpad.net/~maria-discuss>
> Post to : maria-discuss@xxxxxxxxxxxxxxxxxxx <mailto:maria-discuss@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~maria-discuss <https://launchpad.net/~maria-discuss>
> More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-discuss
> Post to : maria-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help : https://help.launchpad.net/ListHelp
Follow ups
References