9.1.1 Specifying the memory sizes

The following figure shows the configuration of memory used by an EADS server.

The explicit heap consists of the following areas:

• Area for storing the history of update operations

• In memory caches and two-way caches, the area for storing the value part of key-value pairs

The history of update operations includes the API functions and information about keys and values. The history of update operations is used to ensure data consistency when data is being replicated.

If a failure occurs during consensus processing, another active EADS server takes the place of the EADS server where the failure occurred, and this other active EADS server participates in the consensus processing on the basis of this history. This history log is retained until the consensus and write processing for the previous update operation is completed.

The history of update operations is deleted automatically when the EADS server determines it to be no longer needed.

Approach

Determine the Java heap size and the explicit heap size per EADS server by referencing 4.1.2 Estimating the Java heap size and 4.1.3 Estimating the explicit heap size.

To Page Top