With VMware Tanzu GemFire for Kubernetes Cluster disk stores, you can persist data to disk as a backup to your in-memory copy and overflow data to disk when memory use gets too high.
Overflow and persistence use disk stores individually or together to store data.
Disk store files include store management files, access control files, and the operation log, or oplog, files, consisting of one file for deletions and another for all other operations.
At creation, each operation log is initialized at the disk store’s
max-oplog-size, with the size divided between the
drffiles. When the oplog is closed, VMware Tanzu GemFire for Kubernetes Cluster shrinks the files to the space used in each file.
In addition to the disk stores you specify, VMware Tanzu GemFire for Kubernetes Cluster has a default disk store that it uses when disk use is configured with no disk store name specified. You can modify default disk store behavior.
Optimize availability and performance by following the guidelines in this section.
This section describes what happens during startup and shutdown and provides procedures for those operations.
gfshcommand-line tool has a number of options for examining and managing your disk stores. The
cache.xmlfile and the DiskStore APIs are your management tools for online and offline disk stores.
A backup is a copy of persisted data from a disk store. A backup is used to restore the disk store to the state it was in when the backup was made. The appropriate back up and restore procedures differ based upon whether the cluster is online or offline. An online system has currently running members. An offline system does not have any running members.