设为首页 收藏本站
查看: 851|回复: 0

[经验分享] MySQL高可用之MHA

[复制链接]
累计签到:1 天
连续签到:1 天
发表于 2015-12-22 12:04:25 | 显示全部楼层 |阅读模式
关闭128主库  shell> mysqladmin -u root -p shutdown
  
  查看切换日志
  shell> tail -f /db/tool/masterha/app1/manager.log
  
  Fri Feb 13 01:19:26 2015 - [warning] Got error on MySQL select ping: 2013 (Lost connection to MySQL server during query)
  Fri Feb 13 01:19:26 2015 - [info] Executing SSH check script: save_binary_logs --command=test --start_pos=4
  --binlog_dir=/mysql/mysql/ --output_file=/var/tmp/save_binary_logs_test
  --manager_version=0.55 --binlog_prefix=mysql-info
  Fri Feb 13 01:19:26 2015 - [info] HealthCheck: SSH to 192.168.90.128 is reachable.
  Fri Feb 13 01:19:29 2015 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.90.128')
  Fri Feb 13 01:19:29 2015 - [warning] Connection failed 3 time(s)..
  Fri Feb 13 01:19:29 2015 - [warning] Master is not reachable from health checker!
  Fri Feb 13 01:19:29 2015 - [warning] Master 192.168.90.128(192.168.90.128:3306) is not reachable!
  Fri Feb 13 01:19:29 2015 - [warning] SSH is reachable.
  Fri Feb 13 01:19:29 2015 - [info] Reading server configurations from /etc/masterha/app1.cnf..
  Fri Feb 13 01:19:30 2015 - [info] Dead Servers:
  Fri Feb 13 01:19:30 2015 - [info]   192.168.90.128(192.168.90.128:3306)
  Fri Feb 13 01:19:30 2015 - [info] Alive Servers:
  Fri Feb 13 01:19:30 2015 - [info]   192.168.90.129(192.168.90.129:3306)
  Fri Feb 13 01:19:30 2015 - [info]   192.168.90.130(192.168.90.130:3306)
  Fri Feb 13 01:19:30 2015 - [info]     Replicating from 192.168.90.128(192.168.90.128:3306)
  Fri Feb 13 01:19:30 2015 - [info]     Not candidate for the new Master (no_master is set)
  Fri Feb 13 01:19:30 2015 - [info] Checking slave configurations..
  Fri Feb 13 01:19:30 2015 - [info] Checking replication filtering settings..
  Fri Feb 13 01:19:30 2015 - [info]  Replication filtering check ok.
  Fri Feb 13 01:19:30 2015 - [info] Master is down!
  Fri Feb 13 01:19:30 2015 - [info] Terminating monitoring script.
  Fri Feb 13 01:19:30 2015 - [info] Got exit code 20 (Master dead).
  Fri Feb 13 01:19:30 2015 - [info] MHA::MasterFailover version 0.55.
  Fri Feb 13 01:19:30 2015 - [info] Starting master failover.
  Fri Feb 13 01:19:30 2015 - [info]
  Fri Feb 13 01:19:30 2015 - [info] * Phase 1: Configuration Check Phase..
  Fri Feb 13 01:19:31 2015 - [info] ** Phase 1: Configuration Check Phase completed.
  Fri Feb 13 01:19:31 2015 - [info]
  Fri Feb 13 01:19:31 2015 - [info] * Phase 2: Dead Master Shutdown Phase..
  Fri Feb 13 01:19:32 2015 - [info] * Phase 2: Dead Master Shutdown Phase completed.
  Fri Feb 13 01:19:32 2015 - [info]
  Fri Feb 13 01:19:32 2015 - [info] * Phase 3: Master Recovery Phase..
  Fri Feb 13 01:19:32 2015 - [info]
  Fri Feb 13 01:19:32 2015 - [info] * Phase 3.1: Getting Latest Slaves Phase..
  Fri Feb 13 01:19:32 2015 - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
  Fri Feb 13 01:19:33 2015 - [info] * Phase 3.3: Determining New Master Phase..
  
  Fri Feb 13 01:19:33 2015 - [info] New master is 192.168.90.129(192.168.90.129:3306)
  Fri Feb 13 01:19:33 2015 - [info] Starting master failover..
  Fri Feb 13 01:19:33 2015 - [info]
  From:
  192.168.90.128 (current master)
  +--192.168.90.129
  +--192.168.90.130
  
  To:
  192.168.90.129 (new master)
  +--192.168.90.130
  Fri Feb 13 01:19:33 2015 - [info]
  Fri Feb 13 01:19:33 2015 - [info] * Phase 3.3: New Master Diff Log Generation Phase..
  Fri Feb 13 01:19:33 2015 - [info] * Phase 3.4: Master Log Apply Phase..
  Fri Feb 13 01:19:33 2015 - [info] Setting read_only=0 on 192.168.90.129(192.168.90.129:3306)..
  Fri Feb 13 01:19:33 2015 - [info]  ok.
  Fri Feb 13 01:19:33 2015 - [info] ** Finished master recovery successfully.
  Fri Feb 13 01:19:33 2015 - [info] * Phase 3: Master Recovery Phase completed.
  Fri Feb 13 01:19:33 2015 - [info]
  Fri Feb 13 01:19:33 2015 - [info] * Phase 4: Slaves Recovery Phase..
  Fri Feb 13 01:19:33 2015 - [info]
  Fri Feb 13 01:19:33 2015 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
  Fri Feb 13 01:19:34 2015 - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
  Fri Feb 13 01:19:34 2015 - [info]  Resetting slave 192.168.90.130(192.168.90.130:3306) and starting replication
  from the new master 192.168.90.129(192.168.90.129:3306)..
  Fri Feb 13 01:19:34 2015 - [info]  Executed CHANGE MASTER.
  Fri Feb 13 01:19:34 2015 - [info]  Slave started.
  Fri Feb 13 01:19:35 2015 - [info] End of log messages from 192.168.90.130.
  Fri Feb 13 01:19:35 2015 - [info] -- Slave recovery on host 192.168.90.130(192.168.90.130:3306) succeeded.
  Fri Feb 13 01:19:35 2015 - [info] All new slave servers recovered successfully.
  Fri Feb 13 01:19:35 2015 - [info]
  Fri Feb 13 01:19:35 2015 - [info] * Phase 5: New master cleanup phase..
  Fri Feb 13 01:19:35 2015 - [info]
  Fri Feb 13 01:19:35 2015 - [info] Resetting slave info on the new master..
  Fri Feb 13 01:19:35 2015 - [info]  192.168.90.129: Resetting slave info succeeded.
  Fri Feb 13 01:19:35 2015 - [info] Master failover to 192.168.90.129(192.168.90.129:3306) completed successfully.
  Fri Feb 13 01:19:35 2015 - [info]
  
  ----- Failover Report -----
  
  app1: MySQL Master failover 192.168.90.128 to 192.168.90.129 succeeded
  
  Master 192.168.90.128 is down!
  
  Check MHA Manager logs at rac1:/db/tool/masterha/app1/manager.log for details.
  
  Started automated(non-interactive) failover.

  The latest slave 192.168.90.129(192.168.90.129:3306) has all>  Selected 192.168.90.129 as a new master.
  192.168.90.129: OK: Applying all logs succeeded.

  192.168.90.130: This host has the latest>
  Generating>  192.168.90.130: OK: Applying all logs succeeded. Slave started, replicating from 192.168.90.129.
  192.168.90.129: Resetting slave info succeeded.
  Master failover to 192.168.90.129(192.168.90.129:3306) completed successfully.
  
  
  重新启动128主库
  shell> masterha_check_repl --conf=/etc/masterha/app1.cnf  
  ...
  Tue Mar 17 14:04:36 2015 - [info]
  192.168.90.129 (current master)
  +--192.168.90.128
  +--192.168.90.130
  
  Tue Mar 17 14:04:36 2015 - [info] Checking replication health on 192.168.90.128..
  Tue Mar 17 14:04:36 2015 - [info]  ok.
  Tue Mar 17 14:04:36 2015 - [info] Checking replication health on 192.168.90.130..
  Tue Mar 17 14:04:36 2015 - [info]  ok.
  Tue Mar 17 14:04:36 2015 - [warning] master_ip_failover_script is not defined.
  Tue Mar 17 14:04:36 2015 - [warning] shutdown_script is not defined.
  Tue Mar 17 14:04:36 2015 - [info] Got exit code 0 (Not master dead).
  
  MySQL Replication Health is OK.

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-154744-1-1.html 上篇帖子: MySQL 5.6.21下载安装之下载篇(一) 下篇帖子: MySQL GTID复制
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表