| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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 mode when the main resource is failed. The resource in this group only operates at the operating nodes.
For instance, a virtual IP address cannot be used at the operating node and the standby node at the same time. In addition, if a virtual IP address causes troubles, it will switch service to the standby node.
Support Parallel Group
A parallel group is a group composed of the resources that can be run at more than one node at the same time.
A parallel group does not failover.In general, the resource containing applications made of cluster is online at the operating node and offline at the standby node. However, if you use a parallel group, you can start, monitor or terminate the designated application at the both nodes.
For instance, if the both nodes operate the backup software and you register it as the resource managed in a cluster, you can run the backup software at the both nodes at the same time. (But, the application should be run at multiple nodes in parallel.)
Support Single Node Group
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.
...
| Attribute | Description | Type | Defaults | Edit | Note |
ClusterName | It is the name of the cluster. | 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 data, Heartbeat data is transferred at an interval 1/10 of this time. | INTEGER | 2000ms | O | |
HBPort | It indicated the heartbeat server port. | 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 indicates 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. | INTEGER | 30sec | O | |
| PingRetryTime | Time to determine ping test failure. | INTEGER | 0sec | O | |
ResourceLimit | It is a maximum number of resources that can be added. | INTEGER | 500ea | X | |
RMIConnectionTimeout | It is RMI connection timeout. | INTEGER | 2sec | O | |
| SingleNodeCluster | It is a cluster consist of a node. | BOOLEAN | false | X | |
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 |
...