ws

Thanks!it's too complex!

Yes,I worry about the single point of failue，if the local consul agent is down,everything is down.It's terriable in production

I'm learning about corosync...

The single-point failure,i mean, replication-manager is alive but only local consul agent is down

normal status: [root@orabackup /root]$ date&&nslookup write_mysql57.service.consul Mon Sep 17 15:44:42 CST 2018 Server: 172.17.11.242 Address: 172.17.11.242#53 Name: write_mysql57.service.consul Address: 172.17.5.101 [root@orabackup /root]$ date&&nslookup read_mysql57.service.consul Mon Sep 17 15:44:56 CST 2018...

> As i known,until now replication-manager still not support remote consul cluster,and when the local consul client is down,replication-manager will automate unregister services. It seems like will unregister services when...

Yes,thanks! :)

Thanks! I have two slaves,when the master(172.17.11.242) is dead,the left two slaves(172.17.5.101,172.17.5.201) compose a new replication topology,for example:master(172.17.5.201)-->slave(172.17.5.101) In my mind,it should be like below: [root]# date&&nslookup read_mysql57.service.consul Thu Sep...

Well,not yet, i'll check it later!

Hi,the problem still exists! [root]# date&&nslookup read_mysql57.service.consul Fri Sep 14 10:31:47 CST 2018 Server: 172.17.5.201 Address: 172.17.5.201#53 ** server can't find read_mysql57.service.consul: NXDOMAIN mrm log: INFO[2018-09-14T10:30:13+08:00] Master Failure detected! Retry...