Vip address not visible in MySQL MMM Architecture

Vip address not visible in MySQL MMM Architecture

After you build a high-availability MySQL MMM (Master-Master Replication Manager) architecture, you cannot see the vip address, after finding a large number of articles on the Internet and observing them, I finally found a way to find the vip address. Now I will share it with you.

1. Check the status of each node on the mmm Monitoring Server

[Root @ node2 bin] # mmm_control show
Db2 (192.168.56.105) master/ONLINE. Roles: writer (192.168.56.100)
Node1 (192.168.56.102) master/ONLINE. Roles: reader (192.168.56.200)

[Root @ node2 bin] #

2. There should be a vip address 192.168.56.100 on the db2 node.

[Root @ db2 bin] # ip
1: lo: <LOOPBACK, UP, LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
Link/loopback 00: 00: 00: 00: 00: 00 brd 00: 00: 00: 00: 00: 00
Inet 127.0.0.1/8 scope host lo
Inet6: 1/128 scope host
Valid_lft forever preferred_lft forever
2: eth0: <BROADCAST, MULTICAST, UP, LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
Link/ether 08: 00: 27: e0: ac: 97 brd ff: ff
Inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
Inet6 fe80: a00: 27ff: fee0: ac97/64 scope link
Valid_lft forever preferred_lft forever
3: eth1: <BROADCAST, MULTICAST, UP, LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
Link/ether 08: 00: 27: a1: d1: 2d brd ff: ff
Inet 192.168.56.105/24 brd 192.168.56.255 scope global eth1
Inet 192.168.56.100/32 scope global eth1 -- this is the vip write address.
Inet6 fe80: a00: 27ff: fea1: d12d/64 scope link
Valid_lft forever preferred_lft forever
[Root @ db2 bin] #

3. There should be a vip address 192.168.56.200 on the node1 node.

[Root @ node1 ~] # Ip
1: lo: <LOOPBACK, UP, LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
Link/loopback 00: 00: 00: 00: 00: 00 brd 00: 00: 00: 00: 00: 00
Inet 127.0.0.1/8 scope host lo
Inet6: 1/128 scope host
Valid_lft forever preferred_lft forever
2: eth0: <BROADCAST, MULTICAST, UP, LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
Link/ether 08: 00: 27: 8e: fe: c6 brd ff: ff
Inet 192.168.56.102/24 brd 192.168.56.255 scope global eth0
Inet 192.168.56.200/32 scope global eth0 -- this is the vip read address
Inet6 fe80: a00: 27ff: fe8e: fec6/64 scope link
Valid_lft forever preferred_lft forever
3: eth1: <BROADCAST, MULTICAST, UP, LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
Link/ether 08: 00: 27: 65: 75: 66 brd ff: ff
Inet 10.0.3.15/24 brd 10.0.3.255 scope global eth1
Inet6 fe80: a00: 27ff: fe65: 7566/64 scope link
Valid_lft forever preferred_lft forever
[Root @ node1 ~] #

Test the MMM high-availability architecture of MySQL

MySQL-MMM for MySQL High Availability

MySQL-MMM switching demonstration

Mysql proxy and MySQL-MMM achieve high availability of read/write splitting

Restore the MySQL-MMM Master from the REPLICATION_FAIL status

Use MySQL-MMM in CentOS to achieve high MySQL availability

This article permanently updates the link address: