Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cluster Configuration

Two Node Cluster

There are 3 types of a group which is configured with two nodes as follows.

  • support failover group
  • support parallel group
  • support single node group

 

For more details about each item above, it will be provided in sequence from the next section.

Support Failover Group

A failover group is a group that contains the resource that can be run at a single node at a time.
A failover group switches to the standby node when the managed resource is failed. The resource in this group only runs at the available nodes.
For instance, a virtual IP address cannot be used at the active node and the standby node at the same time. In addition, if a virtual IP address causes troubles, it will failover the group to the standby node.

...

A single node group is a group of resources that can be run at a single node.
A single node group does not failover. When the included resource experiences troubles, a single node group will try to be online as many times as designated.


Single Node Cluster

This indicates a cluster configured with a resource available to be ran on one single node. single node cluster does not failover. For this type of a cluster, single node group is supported only.

...

The below table explains some attributes.

Image RemovedImage Added

[Figure] Cluster Attribute View

...

Attribute

Description

Type

Defaults

Edit

Note

ClusterName

It is the name of the cluster. 
It is defined during the first time configuring the heartbeat.

NAME

 

X

 

GroupLimit

It is a maximum number of groups that can be added.

INTEGER

32ea

X

 

HBInterval

It is an interval for checking whether to receive heartbeat signal, Heartbeat signal is transferred at an interval 1/10 of this time.

INTEGER

2000ms

O

 

HBPort

It is the heartbeat service port number.

PORT

14321

X

 

HBTimeout

It is ICMP test timeout for heartbeat network. If heartbeat data is disconnected, Timeout will take place, and the ICMP test will be conducted.

INTEGER

3sec

O

 

IsolationTestTmeout

It sets up the ICMP test timeout during the node isolation (SPLIT) test. For the test IP address, please refer to 'Isolation TestAddress' from Node Attribute of this chapter.

INTEGER

3sec

O

 

LogBackupCount

It is the limit of backuped log file count.

INTEGER

3ea

O

 

LogFileSize

It is the size of the log file. Minimum size is 64KB. while the maximum size is 10,000MB. If the size of the log file is greater than this, it will be backed up to mccs.log.1

INTEGER

1000Kb

O

 

LogLevel

It is the standard level of the log recorded in the log file. The log levels include DEBUG, INFO, WARN, ERROR and FATAL, and only those logs above this level will be recorded in the file.

LOG LEVEL

Info

O

 

NodeFaultDetectionTime

It is the time for detecting node failures. 
If the time from the last hearbeat disconnection to the disconnection of the second behind heartbeats exceeds this time, it will be regarded as SPLIT, and if smaller, it will be considered a node failure.

INTEGER

30sec

O

 
PingRetryTime

Time to determine ping test failure.
If the heartbeat data disconnects, it will try to ping during this time. If ping does not work after the time is exceed, it is determine as failure.

INTEGER0secO 

ResourceLimit

It is a maximum number of resources that can be added.

INTEGER

500ea

X

 

RMIConnectionTimeout

It is RMI connection timeout.

INTEGER

2sec

O

 
RuntimeExcuteTimeoutIt limits running time, when executing OS commands, to a setting value.INTEGER10초10secO
SingleNodeClusterIt is a cluster consist of a node.BOOLEANfalseX 

SysLogLevel

It indicated the log level to be recorded in the Windows system log. Only those logs above this level will be recorded in the system log.

LOG LEVEL

Error

O

 

...