【Mysql】Mysql 从库每隔一段时间就重启

发布时间:2020-08-11 13:59:01 作者:小亮520cl
来源:ITPUB博客 阅读:265
背景:HuaYun_Interface-SLAVE从库每隔一段时间slave复制进程便停掉,zabbix发送告警短信
  1. mysql> show slave status\G;
  2. *************************** 1. row ***************************
  3.                Slave_IO_State:
  4.                   Master_Host: *****
  5.                   Master_User: repl
  6.                   Master_Port: 3307
  7.                 Connect_Retry: 60
  8.               Master_Log_File: mysql-bin.000195
  9.           Read_Master_Log_Pos: 629275501
  10.                Relay_Log_File: mysql-relay-bin.000521
  11.                 Relay_Log_Pos: 625430128
  12.         Relay_Master_Log_File: mysql-bin.000195
  13.              Slave_IO_Running: No
  14.             Slave_SQL_Running: No


停掉时查看mysql错误日志我们发现端倪
  1. 2016-06-23 14:06:56 32289 [Warning] 'proxies_priv' entry '@ root@sh275' ignored in --skip-name-resolve mode.
    160623 15:03:49 mysqld_safe Number of processes running now: 0
    160623 15:03:49 mysqld_safe mysqld restarted                 -----发现是mysql服务重启了,而我们配置了skip_slave_start(禁止repl进程自动重启),所以复制进程处于down状态
    2016-06-23 15:03:50 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
    2016-06-23 15:03:50 0 [Note] /home/data/mysql/bin/mysqld (mysqld 5.6.24-log) starting as process 22569 ...
    2016-06-23 15:03:50 22569 [Note] Plugin 'FEDERATED' is disabled.
    2016-06-23 15:03:50 22569 [Note] InnoDB: Using atomics to ref count buffer pool pages
    2016-06-23 15:03:50 22569 [Note] InnoDB: The InnoDB memory heap is disabled
    2016-06-23 15:03:50 22569 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2016-06-23 15:03:50 22569 [Note] InnoDB: Memory barrier is not used
    2016-06-23 15:03:50 22569 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2016-06-23 15:03:50 22569 [Note] InnoDB: Using Linux native AIO
    2016-06-23 15:03:50 22569 [Note] InnoDB: Not using CPU crc32 instructions
    2016-06-23 15:03:50 22569 [Note] InnoDB: Initializing buffer pool, size = 10.0G
    2016-06-23 15:03:51 22569 [Note] InnoDB: Completed initialization of buffer pool


同时我们查看zabbix发送的邮件,有linux主机内存报警通知
  1. 告警主机:_HuaYun_Interface-SLAVE
  2. 主机IP: ******
  3. 告警时间:2016.06.23 15:08:06
  4. 告警等级:Average
  5. 告警信息:Lack of available memory on server HuaYun_Interface-SLAVE
  6. 问题详情:Available memory:163.15 MB
  7. 事件ID: 42590

登上主机检查
  1. [root@NEW-APP-MYSQL-SLAVE ~]# dmesg 
  2. Out of memory: Kill process 32289 (mysqld) score 966 or sacrifice child
  3. Killed process 32289, UID 498, (mysqld) total-vm:14630648kB, anon-rss:7711284kB, file-rss:360kB
[root@NEW-APP-MYSQL-SLAVE ~]# free -m
             total       used       free     shared    buffers     cached
Mem:          7872       7747        124          0        124       1331
-/+ buffers/cache:       6292       1580
Swap:         2047         56       1991




很明显是linux内存不足而发生了OOM killer现象,没办法,加大主机内存吧



推荐阅读:
  1. MySQL主从复制性能优化
  2. 让那些mysql里睡觉的进程,悄悄的死去吧。

免责声明:本站发布的内容(图片、视频和文字)以原创、转载和分享为主,文章观点不代表本网站立场,如果涉及侵权请联系站长邮箱:is@yisu.com进行举报,并提供相关证据,一经查实,将立刻删除涉嫌侵权内容。

mysql 一段时间 每隔

上一篇:[MySQL] 从业务层面对MySQL高可用方案进行分解

下一篇:解决phpcms中get乱码的方法

相关阅读

您好,登录后才能下订单哦!

密码登录
登录注册
其他方式登录
点击 登录注册 即表示同意《亿速云用户服务条款》