|Disk Storage / Configuring Disk Stores|
You define your disk stores in <disk-store> subelements of your cache declaration in cache.xml. All disk stores are available for use by all of your regions and queues.
These <disk-store> attributes and subelements in have corresponding setter and getter methods in the com.gemstone.gemfire.cache.DiskStoreFactory and com.gemstone.gemfire.cache.DiskStore APIs.
|name||String used to identify this disk store. All regions and queues select their disk store by specifying this name.|
|allow-force-compaction||Boolean indicating whether to allow manual compaction through the API or command-line tools.||false|
|auto-compact||Boolean indicating whether to automatically compact a file when it reaches the compaction-threshold.||true|
|compaction-threshold||Percentage of garbage allowed in the file before it is eligible for compaction. Garbage is created by entry destroys, entry updates, and region destroys and creates. Surpassing this percentage does not make compaction occur—it makes the file eligible to be compacted when a compaction is done.||50|
|max-oplog-size||The largest size, in megabytes, to allow an operation log to become before automatically rolling to a new file. This size is the combined sizes of the oplog files.||1024|
|queue-size||For asynchronous queueing. The maximum number of operations to allow into the write queue before automatically flushing the queue. Operations that would add entries to the queue block until the queue is flushed. A value of zero implies no size limit. Reaching this limit or the time-interval limit will cause the queue to flush.||0|
|time-interval||For asynchronous queueing. The number of milliseconds that can elapse before data is flushed to disk. Reaching this limit or the queue-size limit causes the queue to flush.||1000|
|write-buffer-size||Size of the buffer used to write to disk.||32768|
|<disk-dirs>||Defines the system directories where the disk store is written and their maximum sizes.||. with no size limit|
You can specify any number of disk-dir subelements to the disk-dirs element. The data is spread evenly among the active disk files in the directories, keeping within any limits you set.
<disk-dirs> <disk-dir>/host1/users/gf/memberA_DStore</disk-dir> <disk-dir>/host2/users/gf/memberA_DStore</disk-dir> <disk-dir dir-size="20480">/host3/users/gf/memberA_DStore</disk-dir> </disk-dirs>
Use different disk-dir specifications for different disk stores. You cannot use the same directory for the same named disk store in two different members.