Modifying the Default Disk Store

This topic explains how to modify the default VMware Tanzu GemFire disk store.

You can modify the behavior of the default disk store by specifying the attributes you want for the disk store named DEFAULT.

Whenever you use disk stores without specifying the disk store to use, Tanzu GemFire uses the disk store named DEFAULT.

For example, these region and queue configurations specify persistence and/or overflow, but do not specify the disk-store-name. Because no disk store is specified, these use the disk store named DEFAULT.

Examples of using the default disk store for region persistence and overflow:

• gfsh:

  gfsh>create region --name=regionName --type=PARTITION_PERSISTENT_OVERFLOW
  

• cache.xml

  <region refid="PARTITION_PERSISTENT_OVERFLOW"/>
  

Example of using the default disk store for server subscription queue overflow (cache.xml):

<cache-server port="40404">
    <client-subscription eviction-policy="entry" capacity="10000"/>
</cache-server>

Change the Behavior of the Default Disk Store

Tanzu GemFire initializes the default disk store with the default disk store configuration settings. You can modify the behavior of the default disk store by specifying the attributes you want for the disk store named DEFAULT. The only thing that cannot be changed about the default disk store is the name.

The following example changes the default disk store to allow manual compaction and to use multiple, non-default directories:

cache.xml:

<disk-store name="DEFAULT" allow-force-compaction="true">
    <disk-dirs>
        <disk-dir>/export/thor/customerData</disk-dir>
        <disk-dir>/export/odin/customerData</disk-dir>
        <disk-dir>/export/embla/customerData</disk-dir>
    </disk-dirs>
</disk-store>