lt too large (fd=11112)  12 Apr 11:25:53.063 # Error registering fd event for the new client: Resu lt too large (fd=11144)  12 Apr 11:25:53.095 # Error registering fd event for the new client: Resu
redis-2.8.19>redis-server.exe  19 Apr 15:41:03.974 # The Windows version of Redis allocates a large memory mapped file for sharing the heap with the forked process used in persistence operations. This file will be created in the current working directory or the directory specified by the 'heapdir' directive in the .conf file. Windows is reporting that there is insufficient disk space available for this file (Windows error 0x70).
You may fix this problem by either reducing the size of the Redis heap with the --maxheap flag, or by moving the heap file to a local drive with sufficient space. Please see the documentation included with the binary distributions for more details on the --maxheap and --heapdir flags.
# The Linux version of Redis relies on the system call fork() to perform # point-in-time snapshots of the heap. In addition to the AOF and RDB backup # mechanism, the master-slave synchronization and clustering features are # dependent on this behavior of fork(). In order for the Windows version to # perform like the Linux version we had to simulate this aspect of fork(). # Doing so meant moving the Redis heap into a memory mapped file that can # be shared with a child process. # # *** There must be disk space available for this file in order for Redis # to launch. *** The default configuration places this file in the local # appdata directory. If you wish to move this file to another local disk, # use the heapdir flag as described below. # # The maxheap flag controls the maximum size of this memory mapped file, # as well as the total usable space for the Redis heap. Running Redis # without either maxheap or maxmemory will result in a memory mapped file # being created that is equal to the size of physical memory. During # fork() operations the total page file commit will max out at around: # # (size of physical memory) + (2 * size of maxheap) # # For instance, on a machine with 8GB of physical RAM, the max page file # commit with the default maxheap size will be (8)+(2*8) GB , or 24GB. The # default page file sizing of Windows will allow for this without having # to reconfigure the system. Larger heap sizes are possible, but the maximum # page file size will have to be increased accordingly. # # The Redis heap must be larger than the value specified by the maxmemory # flag, as the heap allocator has its own memory requirements and # fragmentation of the heap is inevitable. If only the maxmemory flag is # specified, maxheap will be set at 1.5*maxmemory. If the maxheap flag is # specified along with maxmemory, the maxheap flag will be automatically # increased if it is smaller than 1.5*maxmemory. # # maxheap <bytes>
# The heap memory mapped file must reside on a local path for heap sharing # between processes to work. A UNC path will not suffice here. For maximum # performance this should be located on the fastest local drive available. # This value defaults to the local application data folder(e.g., # "%USERPROFILE%\AppData\Local"). Since this file can be very large, you # may wish to place this on a drive other than the one the operating system # is installed on. # # Note that you must specify a directory here, not a file name. # heapdir <directory path(absolute or relative)>