84669 person learning
152542 person learning
20005 person learning
5487 person learning
7821 person learning
359900 person learning
3350 person learning
180660 person learning
48569 person learning
18603 person learning
40936 person learning
1549 person learning
1183 person learning
32909 person learning
MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk.
提升上面的这个错误 不知道为什么 我找了很多答案 网上的朋友提示这样:config set stop-writes-on-bgsave-error no把这个配置关闭了 请问下 关闭了这个会有什么影响吗???
小伙看你根骨奇佳,潜力无限,来学PHP伐。
config set stop-writes-on-bgsave-error no
Just ignore the error, your rdb persistence will still be wrong, causing the rdb backup to become invalid. It’s best to check if your problem arises:
Whether the redis program user has read and write permissions for the rdb file.
rdbforkWhen the child process backs up data, the memory occupied by redis will double. Check whether your server has enough memory at this time.
fork
Does the file not have write permission?
Those with read and write permissions
RDB是Redis持久化方式的一种,会定期在磁盘上做持久化操作。目测是因为RedisNo permission to write to disk.
RDB
Redis
Refer to this article http://www.cnblogs.com/qq7829...
It says to add vm.overcommit_memory = 1 in /etc/sysctl.conf and then restart to solve the problem. Let’s try it and see if it can be solved
Also check if your disk is full. This problem will also occur in this case. You can use the command df -h to check the disk usage
df -h
Just ignore the error, your rdb persistence will still be wrong, causing the rdb backup to become invalid. It’s best to check if your problem arises:
Whether the redis program user has read and write permissions for the rdb file.
rdb
fork
When the child process backs up data, the memory occupied by redis will double. Check whether your server has enough memory at this time.Does the file not have write permission?
Those with read and write permissions
RDB
是Redis
持久化方式的一种,会定期在磁盘上做持久化操作。目测是因为
Redis
No permission to write to disk.Refer to this article http://www.cnblogs.com/qq7829...
It says to add vm.overcommit_memory = 1 in /etc/sysctl.conf and then restart to solve the problem. Let’s try it and see if it can be solved
Also check if your disk is full. This problem will also occur in this case. You can use the command
df -h
to check the disk usage