|
n Apr 20 14:30:43 2015 - [info] Resetting slave vdbsrv3(192.168.1.8:3306) and starting replication from the new master vdbsrv2(192.168.1.7:3306)..
Mon Apr 20 14:30:43 2015 - [info] Executed CHANGE MASTER.
Mon Apr 20 14:30:43 2015 - [info] Slave started.
Mon Apr 20 14:30:43 2015 - [info] End of log messages from vdbsrv3.
Mon Apr 20 14:30:43 2015 - [info] -- Slave recovery on host vdbsrv3(192.168.1.8:3306) succeeded.
Mon Apr 20 14:30:43 2015 - [info] All new slave servers recovered successfully.
Mon Apr 20 14:30:43 2015 - [info]
Mon Apr 20 14:30:43 2015 - [info] * Phase 5: New master cleanup phase..
Mon Apr 20 14:30:43 2015 - [info]
Mon Apr 20 14:30:43 2015 - [info] Resetting slave info on the new master..
Mon Apr 20 14:30:43 2015 - [info] vdbsrv2: Resetting slave info succeeded.
Mon Apr 20 14:30:43 2015 - [info] Master failover to vdbsrv2(192.168.1.7:3306) completed successfully.
Mon Apr 20 14:30:43 2015 - [info]
----- Failover Report -----
app1: MySQL Master failover vdbsrv1(192.168.1.6:3306) to vdbsrv2(192.168.1.7:3306) succeeded
Master vdbsrv1(192.168.1.6:3306) is down! ###整个failover总时间14:30:43-14:30:19=24s
Check MHA Manager logs at vdbsrv4:/var/log/masterha/app1/manager.log for details.
Started automated(non-interactive) failover.
Invalidated master IP address on vdbsrv1(192.168.1.6:3306)
The latest slave vdbsrv2(192.168.1.7:3306) has all relay logs for recovery.
Selected vdbsrv2(192.168.1.7:3306) as a new master.
vdbsrv2(192.168.1.7:3306): OK: Applying all logs succeeded.
vdbsrv2(192.168.1.7:3306): OK: Activated master IP address.
vdbsrv3(192.168.1.8:3306): Generating differential relay logs up to vdbsrv2(192.168.1.7:3306)succeeded.
Generating relay diff files from the latest slave succeeded.
vdbsrv3(192.168.1.8:3306): OK: Applying all logs succeeded. Slave started, replicating from vdbsrv2(192.168.1.7:3306)
vdbsrv2(192.168.1.7:3306): Resetting slave info succeeded.
Master failover to vdbsrv2(192.168.1.7:3306) completed successfully.
?
|