mha manager启动的时候做的操作

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

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

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 slave xxx.h.lmlc(xx3333).
Thu Apr 27 16:42:58 2017 - [warning] relay_log_purge=0 is not set on slave xx3.h.lmlc(xxx:3333).
Thu Apr 27 16:42:58 2017 - [info] read_only=1 is not set on slave biee(xxx:3333).
Thu Apr 27 16:42:58 2017 - [warning] relay_log_purge=0 is not set on slave biee(xx3333).
Thu Apr 27 16:42:58 2017 - [info] Checking replication filtering settings..
Thu Apr 27 16:42:58 2017 - [info] binlog_do_db= , binlog_ignore_db=
Thu Apr 27 16:42:58 2017 - [info] Replication filtering check ok.
Thu Apr 27 16:42:58 2017 - [info] GTID (with auto-pos) is not supported
Thu Apr 27 16:42:58 2017 - [info] Starting SSH connection tests..
Thu Apr 27 16:43:00 2017 - [info] All SSH connection tests passed successfully.
Thu Apr 27 16:43:00 2017 - [info] Checking MHA Node version..
Thu Apr 27 16:43:01 2017 - [info] Version check ok.
Thu Apr 27 16:43:01 2017 - [info] Checking SSH publickey authentication settings on the current master..
Thu Apr 27 16:43:01 2017 - [info] HealthCheck: SSH to xxxx is reachable.
Thu Apr 27 16:43:02 2017 - [info] Master MHA Node version is 0.56.
Thu Apr 27 16:43:02 2017 - [info] Checking recovery script configurations on xxx(xxx:3333)..
Thu Apr 27 16:43:02 2017 - [info] Executing command: save_binary_logs –command=test –start_pos=4 –binlog_dir=/data/mysql_3333 –output_file=/mha/workdir/3333/save_binary_logs_test –manager_version=0.56 –start_file=mysql-bin.000007
Thu Apr 27 16:43:02 2017 - [info] Connecting to concert@xx(xxxx:88)..
Creating /mha/workdir/3333 if not exists.. ok.
Checking output directory is accessible or not..
ok.
Binlog found at /data/mysql_3333, up to mysql-bin.000007
Thu Apr 27 16:43:02 2017 - [info] Binlog setting check done.
Thu Apr 27 16:43:02 2017 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Thu Apr 27 16:43:02 2017 - [info] Executing command : apply_diff_relay_logs –command=test –slave_user=’masterha’ –slave_host=xxxx.h.lmlc –slave_ip=xxx –slave_port=3333 –workdir=/mha/workdir/3333 –target_version=5.6.25-log –manager_version=0.56 –relay_dir=/data/mysql_3333 –current_relay_log=xxx-relay-bin.000006 –slave_pass=xxx
Thu Apr 27 16:43:02 2017 - [info] Connecting to concert@xxx(xxx.h.lmlc:88)..
Checking slave recovery environment settings..
Relay log found at /data/mysql_3333, up to xxx-relay-bin.000007
Temporary relay log file is /data/mysql_3333/xxx-relay-bin.000007
Testing mysql connection and privileges..Warning: Using a password on the command line interface can be insecure.
done.
Testing mysqlbinlog output.. done.
Cleaning up test file(s).. done.
Thu Apr 27 16:43:03 2017 - [info] Executing command : apply_diff_relay_logs –command=test –slave_user=’masterha’ –slave_host=biee –slave_ip=xxx –slave_port=3333 –workdir=/mha/workdir/3333 –target_version=5.6.25-log –manager_version=0.56 –relay_dir=/data/mysql_3333 –current_relay_log=biee-relay-bin.000003 –slave_pass=xxx
Thu Apr 27 16:43:03 2017 - [info] Connecting to concert@xxxx(biee:88)..
Checking slave recovery environment settings..
Relay log found at /data/mysql_3333, up to biee-relay-bin.000004
Temporary relay log file is /data/mysql_3333/biee-relay-bin.000004
Testing mysql connection and privileges..Warning: Using a password on the command line interface can be insecure.
done.
Testing mysqlbinlog output.. done.
Cleaning up test file(s).. done.
Thu Apr 27 16:43:03 2017 - [info] Slaves settings check done.
Thu Apr 27 16:43:03 2017 - [info]
xx(xxx:3333) (current master)
+–xxxx.h.lmlc(xxx:3333)
+–biee(xxxx:3333)

Thu Apr 27 16:43:03 2017 - [info] Checking master_ip_failover_script status:
Thu Apr 27 16:43:03 2017 - [info] /home/dba_scripts/masterha/master_ip_failover.sh –command=status –ssh_user=xx –orig_master_host=xxx –orig_master_ip=xxx –orig_master_port=3333 –orig_master_ssh_port=88
2017-04-27 16:43:03 master_ip_failover.sh [info]: ————-start check————
Thu Apr 27 16:43:03 2017 - [info] OK.
Thu Apr 27 16:43:03 2017 - [info] Checking shutdown script status:
Thu Apr 27 16:43:03 2017 - [info] /home/dba_scripts/masterha/power_manager.sh –command=status –ssh_user=xx –host=xxx –ip=xx –ssh_port=88
————-power off script do not power off machine————-
Thu Apr 27 16:43:03 2017 - [info] OK.
Thu Apr 27 16:43:03 2017 - [info] Set master ping interval 3 seconds.
Thu Apr 27 16:43:03 2017 - [warning] secondary_check_script is not defined. It is highly recommended setting it to check master reachability from two or more routes.
Thu Apr 27 16:43:03 2017 - [info] Starting ping health check on xxx(xxx:3333)..
Thu Apr 27 16:43:03 2017 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn’t respond..

在master宕掉后,manager会连续ping3次,都不同就开始转移

### 如何在Linux系统上彻底卸载MHA Manager 对于MHA (Master High Availability) Manager的卸载,通常需要遵循一系列特定的操作来确保其被完全移除。由于提供的引用并未涉及MHA Manager的具体卸载指南,下面的信息基于常规软件包管理和配置文件清理的最佳实践。 #### 使用包管理器卸载MHA Manager 如果通过官方源或第三方仓库安装了MHA,则可以利用系统的包管理工具来进行初步的删除操作: 对于Ubuntu/Debian系统: ```bash sudo apt-get remove --purge mha4mysql-manager ``` 这条命令不仅会移除mha4mysql-manager本身,还会清除所有关联的数据和设置[^1]。 #### 手动清理残留文件 即使已经使用`apt-get purge`进行了处理,仍可能存在一些自定义路径下的日志、临时文件或其他由管理员手工创建的相关资源未被触及。建议检查并手动删除这些位置中的任何遗留项: - `/etc/mha/`: 配置目录 - `/var/log/masterha/`: 日志存储区 - 用户家目录内的隐藏文件夹如`.masterha*` 注意,在执行此类操作前应当确认确实不再需要保存其中的内容以防误删重要资料[^2]。 #### 移除环境变量与启动脚本 有时为了方便调用程序功能会在shell profile里加入指向MHA二进制的位置;另外也可能存在开机自动加载的服务单元文件。务必审查以下方面是否存在相关内容,并适当调整: - `.bashrc`, `.zshrc`等Shell初始化脚本内关于PATH修改的部分; - Systemd service definitions under `/lib/systemd/system/` or `/etc/init.d/`. 完成以上步骤之后重启计算机使更改生效即可认为完成了对MHA Manager较为彻底的卸载过程[^3].
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值