Hitachi

In-Memory Data Grid Hitachi Elastic Application Data Store


7.5.3 Cluster configuration-dependent parameters

The table below lists the parameters that depend on the cluster configuration.

Bold typeface indicates a required parameter.

Table 7‒6: List of cluster configuration-dependent parameters

No.

Property file

Parameter name

Value to be specified

Default value

1

Cluster property file

eads.node.EADS-server-ID.address

IP address or host name

None

2

eads.node.EADS-server-ID.port

Port number

None

3

eads.node.EADS-server-ID.position

-2147483648 to 2147483647

None

4

Shared property file

eads.failureDetector.heartbeat.address

IP address (multicast address)

239.255.2.1

5

eads.failureDetector.heartbeat.port

Port number

24630

6

eads.replication.factor

1 to 5

2

Important note

The contents of the cluster property files and the shared property files must be identical among all the EADS servers that make up a cluster. If the properties differ, the EADS servers cannot start because the cluster cannot be configured.

If a value that is specified is outside the range of permissible values, the default value is set.

Organization of this subsection

(1) Cluster property file

(a) eads.node.EADS-server-ID.address

This parameter specifies the IP addresses or host names (the eads.server.address parameter value in the server properties) of the EADS servers that make up the cluster.

If you specify a host name, make sure that a unique IP address can be identified from the specified host name.

EADS-server-ID is a user-assigned number (an integer from 1 through 96). The EADS server IDs are used for the store data file names to uniquely identify the individual EADS servers in the cluster. Although the EADS server IDs need not be sequential, they must be unique within the cluster.

(b) eads.node.EADS-server-ID.port

This parameter specifies the port numbers (the eads.server.port parameter value in the server properties) of the EADS servers that make up the cluster.

EADS-server-ID is a user-assigned number (an integer from 1 through 96). The EADS server IDs are used for the store data file names to uniquely identify the individual EADS servers in the cluster. Although the EADS server IDs need not be sequential, they must be unique within the cluster.

(c) eads.node.EADS-server-ID.position

This parameter specifies a location for an EADS server (hash value).

EADS-server-ID is a user-assigned number (an integer from 1 through 96). The EADS server IDs are used for the store data file names to uniquely identify the individual EADS servers in the cluster. Although the EADS server IDs need not be sequential, they must be unique within the cluster.

This parameter is optional. When this parameter is omitted, the EADS servers are distributed evenly to logical locations in the cluster.

When you use this parameter, specify locations for all EADS servers that make up the cluster. If the parameter is specified for some but not all of the EADS servers, an error occurs and EADS server startup fails.

(2) Shared property file

(a) eads.failureDetector.heartbeat.address

This parameter specifies the IP address (multicast address) used for transmitting heartbeats among the EADS servers.

You can also specify an alias of the IP address.

(b) eads.failureDetector.heartbeat.port

This parameter specifies the port number used for transmitting heartbeats among the EADS servers.

(c) eads.replication.factor

This parameter specifies the data multiplicity.

Important note

The number of EADS servers that make up the cluster must be at least the data multiplicity [Figure] 2 - 1.

An error will result if the number of EADS servers making up the cluster is less than the data multiplicity [Figure] 2 - 1, in which case startup of the EADS servers will fail.