mha manager启动的时候做的操作

最新推荐文章于 2024-07-27 19:38:04 发布

aoerqileng

最新推荐文章于 2024-07-27 19:38:04 发布

阅读量1.2k

点赞数

分类专栏： MYSQL

本文链接：https://blog.csdn.net/aoerqileng/article/details/70860020

版权

这篇博客记录了MHA(Master High Availability) Manager启动时进行的操作，包括检查服务器状态、验证复制配置、SSH连接测试、版本验证、恢复脚本配置检查以及健康检查等。在主服务器宕机后，MHA Manager会进行一系列的检查，如三次连续的ping失败，才会开始故障转移过程。

摘要由CSDN通过智能技术生成

Thu Apr 27 16:42:58 2017 - [info] MHA::MasterMonitor version 0.56.
Thu Apr 27 16:42:58 2017 - [info] GTID failover mode = 0
Thu Apr 27 16:42:58 2017 - [info] Dead Servers:
Thu Apr 27 16:42:58 2017 - [info] Alive Servers:
Thu Apr 27 16:42:58 2017 - [info] hz-xx.h.lmlc(xx:3333)
Thu Apr 27 16:42:58 2017 - [info] hz-xxxx(xxx:3333)
Thu Apr 27 16:42:58 2017 - [info] biee(xxx:3333)
Thu Apr 27 16:42:58 2017 - [info] Alive Slaves:
Thu Apr 27 16:42:58 2017 - [info] xx.h.lmlc(xx:3333) Version=5.6.25-log (oldest major version between slaves) log-bin:enabled
Thu Apr 27 16:42:58 2017 - [info] Replicating from xx(xx:3333)
Thu Apr 27 16:42:58 2017 - [info] Primary candidate for the new Master (candidate_master is set)
Thu Apr 27 16:42:58 2017 - [info] biee(xx:3333) Version=5.6.25-log (oldest major version between slaves) log-bin:enabled
Thu Apr 27 16:42:58 2017 - [info] Replicating from xx(xxx:3333)
Thu Apr 27 16:42:58 2017 - [info] Primary candidate for the new Master (candidate_master is set)
Thu Apr 27 16:42:58 2017 - [info] Current Alive Master: xxx(xxx:3333)
Thu Apr 27 16:42:58 2017 - [info] Checking slave configurations..
Thu Apr 27 16:42:58 2017 - [info] read_only=1 is not set on sl