中秋的时候正在外面愉快的在外卖喝着咖啡玩电脑。。。。。。突发 redis 报警从 sentry 应用端曝出的错误
MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled,
because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option).
Please check the Redis logs for details about the RDB error.
于是又开始愉快的处理问题了，看上去像是执行 rdb 快照持久化的时候出现的问题，上到 redis 机器查看日志定位详细问题
420:M 14 Sep 15:56:27.067 # Can't save in background: fork: Cannot allocate memory 420:M 14 Sep 15:56:33.071 * 10000 changes in 60 seconds. Saving... 420:M 14 Sep 15:56:33.072 # Can't save in background: fork: Cannot allocate memory 420:M 14 Sep 15:56:39.079 * 10000 changes in 60 seconds. Saving... 420:M 14 Sep 15:56:39.080 # Can't save in background: fork: Cannot allocate memory 420:M 14 Sep 15:56:45.083 * 10000 changes in 60 seconds. Saving... 420:M 14 Sep 15:56:45.083 # Can't save in background: fork: Cannot allocate memory 420:M 14 Sep 15:56:51.094 * 10000 changes in 60 seconds. Saving... 420:M 14 Sep 15:56:51.095 # Can't save in background: fork: Cannot allocate memory 420:M 14 Sep 15:56:57.002 * 10000 changes in 60 seconds. Saving...
可以很明显的发现应该是尝试 fork 的时候内存不够，并没有被 linux 内核放行。
这里有两个点我认为需要注意一下，一个是 redis 在默认配置的情况是下是开启参数
stop-writes-on-bgsave-error yes
也就是 如果 bgsave 存储快照失败，那么 redis 将阻止数据继续写入，如果将这个设置成 False 那么即使是 bgsave 快照写入磁盘失败，也不会让 redis 立即对外停止服务。
但是无法 bgsave 让数据落盘始终是隐患，要是机器一重启，就完蛋了。所以我尝试查询一些热修复的手段来修复这个问题。
最终 linux 端有一个参数 vm.overcommit_memory 可以解决这个问题默认参数是 0 ，它有三个值可以配置。
这时候就是内存不足，到了这里，操作系统要怎么办，就要祭出我们的主角“overcommit_memory”参数了（/proc/sys/vm/overcommit_memory）； vm.overcommit_memory = 0 启发策略 比较 此次请求分配的虚拟内存大小和系统当前空闲的物理内存加上swap，决定是否放行。系统在为应用进程分配虚拟地址空间时，会判断当前申请的虚拟地址空间大小是否超过剩余内存大小，如果超过，则虚拟地址空间分配失败。因此，也就是如果进程本身占用的虚拟地址空间比较大或者剩余内存比较小时，fork、malloc等调用可能会失败。 vm.overcommit_memory = 1 允许overcommit 直接放行，系统在为应用进程分配虚拟地址空间时，完全不进行限制，这种情况下，避免了fork可能产生的失败，但由于malloc是先分配虚拟地址空间，而后通过异常陷入内核分配真正的物理内存，在内存不足的情况下，这相当于完全屏蔽了应用进程对系统内存状态的感知，即malloc总是能成功，一旦内存不足，会引起系统OOM杀进程，应用程序对于这种后果是无法预测的。 vm.overcommit_memory = 2 禁止overcommit 根据系统内存状态确定了虚拟地址空间的上限，由于很多情况下，进程的虚拟地址空间占用远大于其实际占用的物理内存，这样一旦内存使用量上去以后，对于一些动态产生的进程(需要复制父进程地址空间)则很容易创建失败，如果业务过程没有过多的这种动态申请内存或者创建子进程，则影响不大，否则会产生比较大的影响 。这种情况下系统所能分配的内存不会超过上面提到的CommitLimit大小，如果这么多资源已经用光，那么后面任何尝试申请内存的行为都会返回错误，这通常意味着此时没法运行任何新程序。 ———————————————— 版权声明：本文为CSDN博主「朱清震」的原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接及本声明。 原文链接：https://blog.csdn.net/zqz_zqz/article/details/53384854
所以这里 bgsave 我们 redis 应用会尝试对主进程进行 fork ，然后内存不够申请未被内核放行。所以 hotfix 我尝试将参数 vm.overcommit_memory 设置成 1 直接进行放行。
/etc/sysctl.conf vm.overcommit_memory=1 sysctl -p
生效，再看日志发现就可以成功了。
这里我找到官方 FAQ 也对类似问题有描述
Background saving fails with a fork() error under Linux even if I have a lot of free RAM!
Short answer:
echo 1 > /proc/sys/vm/overcommit_memory:)And now the long one:
Redis background saving schema relies on the copy-on-write semantic of fork in modern operating systems: Redis forks (creates a child process) that is an exact copy of the parent. The child process dumps the DB on disk and finally exits. In theory the child should use as much memory as the parent being a copy, but actually thanks to the copy-on-write semantic implemented by most modern operating systems the parent and child process will share the common memory pages. A page will be duplicated only when it changes in the child or in the parent. Since in theory all the pages may change while the child process is saving, Linux can't tell in advance how much memory the child will take, so if the
overcommit_memorysetting is set to zero fork will fail unless there is as much free RAM as required to really duplicate all the parent memory pages, with the result that if you have a Redis dataset of 3 GB and just 2 GB of free memory it will fail.Setting
overcommit_memoryto 1 tells Linux to relax and perform the fork in a more optimistic allocation fashion, and this is indeed what you want for Redis.A good source to understand how Linux Virtual Memory works and other alternatives for
overcommit_memoryandovercommit_ratiois this classic from Red Hat Magazine, "Understanding Virtual Memory". Beware, this article had1and2configuration values forovercommit_memoryreversed: refer to the proc(5) man page for the right meaning of the available values.
后来 hotfix 之后，我们清理了一些很久未能释放的大 key，将内存恢复到比较小的水平。就很稳了，这次问题发生之后没有无脑进行重启，而是迅速通过一定的思路来查询问题，感觉自己解决问题的方法稍微成熟了一点点。
Reference:
https://zhuanlan.zhihu.com/p/36872365 fork 的原理及实现
https://stackoverflow.com/questions/11752544/redis-bgsave-failed-because-fork-cannot-allocate-memory redis bgsave failed because fork Cannot allocate memory
https://www.freebsd.org/doc/zh_CN/books/handbook/configtuning-sysctl.html 12.11. 用 sysctl 进行调整
https://blog.csdn.net/zqz_zqz/article/details/53384854 redis Can’t save in background: fork: Cannot allocate memory 解决及原理
https://redis.io/topics/faq 官方 FAQ