Redis log error: [7666] Jan 00:22:36.028 # Error Moving temp DB file on the final destination:invalid cross-device link [1 937] 00:22:36.513 # Background saving error [1937] Jan 00:22:36.614 * 1 changes in seconds. Saving ... [7679] Jan 00:27:15.659 # WARNING Overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ' vm.overcommit_memory = 1 ' to/etc/sysctl.conf and then reboot or run the command ' Sysctl vm.overcom Mit_memory=1 ' for the take effect. [7679] 00:27:35.287 * DB loaded from disk:19.629 seconds processing scheme: As prompted, add:/etc/sysctl.conf in Profile vm.overcommit_memory= 1 Restart Redis For more information about Overcommit_memory: The value is 0, when the system allocates the virtual address space for the application process, it determines whether the virtual address space for the current request exceeds the remaining memory size, and if it is exceeded, the virtual address space allocation fails. Therefore, calls to fork, malloc, and so on may fail if the process itself occupies a larger virtual address space or the remaining memory is less than the hour. With a value of 1, the system is completely unrestricted when assigning virtual address space to the application process, which avoids the possible failure of fork, but because malloc allocates the virtual address space first and then allocates real physical memory through the exception into the kernel, in the case of insufficient memory, This is equivalent to completely masking the application process to the system memory state perception, that is, malloc always succeeds, once the memory is insufficient, will cause the system Oom process, the application for this consequence is unpredictable value of 2, is based on the system memory state determined the upper limit of the virtual address space, by theIn many cases, the virtual address space of a process takes up much of the physical memory it actually occupies, so that once memory usage goes up, it is easy to create a failure for some dynamically generated processes (which need to replicate the parent process address space), if the business process does not have too much of this dynamic request for memory or creates child processes, The effect is not very big, otherwise it will have a relatively large impact
Redis Persistent error failed
