Asynchronous AOF fsync is taking too long (disk is busy?). Writing the AOF buffer without waiting for fsync to complete, this may slow down Redis.

一、问题描述

 

Redis日志:

2110:M 24 Apr 02:01:02.058 * Asynchronous AOF fsync is taking too long (disk is busy?). Writing the AOF buffer without waiting for fsync to complete, this may slow down Redis.
2110:M 24 Apr 02:01:12.862 # Connection with slave client id #58526360 lost.
2110:M 24 Apr 02:01:12.863 # Connection with slave client id #58525913 lost.

sentinal日志:

788:X 24 Apr 02:01:07.970 # +sdown master mymaster 172.16.158.87 6379
1788:X 24 Apr 02:01:08.036 # +odown master mymaster 172.16.158.87 6379 #quorum 2/2
1788:X 24 Apr 02:01:08.037 # +new-epoch 79
1788:X 24 Apr 02:01:08.037 # +try-failover master mymaster 172.16.158.87 6379
1788:X 24 Apr 02:01:12.864 # +vote-for-leader fd5c6228b4f209cfc2c88265a0d47f39879027ab 79
1788:X 24 Apr 02:01:12.865 # +config-update-from sentinel 913c8b2f64f54caf46ff25ac6fa9bdcae86d9d02 172.16.158.85 26379 @ mymaster 172.16.158.87 6379
1788:X 24 Apr 02:01:12.865 # +switch-master mymaster 172.16.158.87 6379 172.16.158.85 6379
1788:X 24 Apr 02:01:12.865 * +slave slave 172.16.158.86:6379 172.16.158.86 6379 @ mymaster 172.16.158.85 6379
1788:X 24 Apr 02:01:12.865 * +slave slave 172.16.158.87:6379 172.16.158.87 6379 @ mymaster 172.16.158.85 6379
1788:X 24 Apr 02:01:12.867 # 913c8b2f64f54caf46ff25ac6fa9bdcae86d9d02 voted for 913c8b2f64f54caf46ff25ac6fa9bdcae86d9d02 79

监控截图

 

 

二、问题原因分析

参考:https://www.cnblogs.com/yangxiaoyi/p/7806406.html

参考:https://blog.csdn.net/ljl890705/article/details/51540427

 

三、解决操作(未验证)

1.修改sysctl vm.dirty_bytes内核参数

echo "vm.dirty_bytes=33554432" >> /etc/sysctl.conf  
sysctl -p

2.修改Redis配置参数 repl-backlog-size

 repl-backlog-size=200mb

 

posted @ 2020-04-24 09:58  百衲本  阅读(1547)  评论(0编辑  收藏  举报
cnblogs_post_body { color: black; font: 0.875em/1.5em "微软雅黑" , "PTSans" , "Arial" ,sans-serif; font-size: 15px; } cnblogs_post_body h1 { text-align:center; background: #333366; border-radius: 6px 6px 6px 6px; box-shadow: 0 0 0 1px #5F5A4B, 1px 1px 6px 1px rgba(10, 10, 0, 0.5); color: #FFFFFF; font-family: "微软雅黑" , "宋体" , "黑体" ,Arial; font-size: 23px; font-weight: bold; height: 25px; line-height: 25px; margin: 18px 0 !important; padding: 8px 0 5px 5px; text-shadow: 2px 2px 3px #222222; } cnblogs_post_body h2 { text-align:center; background: #006699; border-radius: 6px 6px 6px 6px; box-shadow: 0 0 0 1px #5F5A4B, 1px 1px 6px 1px rgba(10, 10, 0, 0.5); color: #FFFFFF; font-family: "微软雅黑" , "宋体" , "黑体" ,Arial; font-size: 20px; font-weight: bold; height: 25px; line-height: 25px; margin: 18px 0 !important; padding: 8px 0 5px 5px; text-shadow: 2px 2px 3px #222222; } cnblogs_post_body h3 { background: #2B6695; border-radius: 6px 6px 6px 6px; box-shadow: 0 0 0 1px #5F5A4B, 1px 1px 6px 1px rgba(10, 10, 0, 0.5); color: #FFFFFF; font-family: "微软雅黑" , "宋体" , "黑体" ,Arial; font-size: 18px; font-weight: bold; height: 25px; line-height: 25px; margin: 18px 0 !important; padding: 8px 0 5px 5px; text-shadow: 2px 2px 3px #222222; } 回到顶部 博客侧边栏 回到顶部 页首代码 回到顶部 页脚代码