Hitachi

In-Memory Data Grid Hitachi Elastic Application Data Store


11.14.1 How to manage available space in the data storage (using only memory caches)

This subsection explains how to monitor available space in the data storage and how to increase available space when using only memory caches.

Organization of this subsection

(1) Monitor available space by using statistics

Estimate the available space in the data storage from the information that is output as statistics by range (eads_store_stats.csv). Monitor these values.

Statistics by range (eads_store_stats.csv) are output only when the total data restriction function is used.

For details about the statistics by range (eads_store_stats.csv), see 11.13.5 Statistics by range (eads_store_stats.csv).

If the available space in the data storage is low, take the actions described in the following subsections.

(a) Deleting unneeded data

Increase the available space in the data storage by deleting unneeded data.

(b) Adding EADS servers to the cluster

If enough space cannot be obtained from (a), add EADS servers to the cluster. Adding EADS servers to the cluster enables you to reduce the number of data items stored in each EADS server.

For details about how to add EADS servers to a cluster, see 11.1.1 How to add EADS servers to a cluster without stopping the cluster (scale-out processing) or 11.1.2 How to add EADS servers to a cluster after stopping the cluster (using only memory caches).

Note that because the total data restriction function is disabled during scale-out processing, sufficient space (at least twice the number of data items and capacity that are added during scale-out processing) is required.

(2) If processing results in an error due to a space shortage

This subsection explains how to handle processing errors that result from a shortage of space.

(a) Check the storage that has reached the maximum amount of data that can be stored on EADS servers

Execute the eztool storeusage command to determine from the number of keys and amount of memory usage the storage that has reached the maximum amount of data that can be stored on EADS servers.

(b) Terminate all EADS servers in the cluster (after exporting data to files)

Export data to files and then terminate all EADS servers in the cluster.

For details about this procedure, see 10.5 Terminating the EADS servers (after exporting data from memory to files).

(c) Change the properties

Re-estimate the Java heap size and the explicit heap size, and then change the properties based on the estimation results. If necessary, add server machines and memory.

For details about how to estimate these values, see the following:

For details about how to change the properties, see 11.4 Changing the properties.

(3) Start all EADS servers in the cluster (and import data from files)

Start all EADS servers in the cluster, and then import back into memory the data that was exported to files during the previous session.

For details about the procedure, see 10.3 Starting the EADS servers (and creating caches by importing data from files).