|Managing Pivotal GemFire / Disk Storage|
At creation, each operation log is initialized at the disk store's max-oplog-size, with the size divided between the crf and drf files. When the oplog is closed, Pivotal GemFire shrinks the files to the space used in each file.
After the oplog is closed, GemFire also attempts to create a krf file, which contains the key names as well as the offset for the value within the crf file. Although this file is not required for startup, if it is available, it will improve startup performance by allowing GemFire to load the entry values in the background after the entry keys are loaded. See How Startup and Shutdown Work with Disk Stores.
This example listing shows the logs in a system with only one disk directory specified for the store. The first log (BACKUPCacheOverflow_1.crf and BACKUPCacheOverflow_1.drf) has been closed and the system is writing to the second log.
bash-2.05$ ls -tlra total 55180 drwxrwxr-x 7 jpearson users 512 Mar 22 13:56 .. -rw-rw-r-- 1 jpearson users 0 Mar 22 13:57 BACKUPCacheOverflow_2.drf -rw-rw-r-- 1 jpearson users 426549 Mar 22 13:57 BACKUPCacheOverflow_2.crf -rw-rw-r-- 1 jpearson users 0 Mar 22 13:57 BACKUPCacheOverflow_1.drf -rw-rw-r-- 1 jpearson users 936558 Mar 22 13:57 BACKUPCacheOverflow_1.crf -rw-rw-r-- 1 jpearson users 1924 Mar 22 13:57 BACKUPCacheOverflow.if drwxrwxr-x 2 jpearson users 2560 Mar 22 13:57 .
The system rotates through all available disk directories to write its logs. The next log is always started in a directory that has not reached its configured capacity, if one exists.
Even though the configured directory size limit has been exceeded a new oplog will be created. The current limit is of XXX. The current space used in the directory is YYY.
Disk is full and rolling is disabled. No space can be created