| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Column | |||||||||||||
| Section | |||||||||||||
|
Cluster Configuration
Two
...
Node Clsuter
Support Failover Group
Failover A failover group is including the resources a group that contains the resource that can be run on only one at a single node at a time.
Application will be switch over to standby node at critical reource is failed in a failover group. The resources that included group are online only available node.
For example, user would like to run backup software on both nodes and be managed by the MCCS, backup software should be online on both nodes at the same time. You can use parallel group instead of failover group for thisA failover group switches to the standby node when the main 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 switch service to the standby node.
Support Parallel Group
Parallel A parallel group is a group composed of the resources that are taken online on can be run at more than two nodes one node at the same time. Parallel group cannot failover.
The opposition of this is Failover Group. The group can be online on a node in a cluster within a failover group. However, when configured through parallel group, specified application can be online, monitored and terminated on the multiple nodes at the same time in a cluster.
For example, user would like to run backup software on both nodes and be managed by the MCCS, backup software should be online on
A parallel group does not failover.In general, the resource containing applications made of cluster is online at the active node and offline at the standby node.
However, if you use a parallel group, you can start, monitor and stop 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. You can use parallel group instead of failover group for this.(But, the application should be run at multiple nodes in parallel.)
Support Single Node Group
한개의 노드에서 실행 될 수 있는 리소스로 구성된 그룹을 싱글 노드 그룹이라고 합니다. 싱글노드 그룹은 페일오버 하지 않습니다.
싱글노드 그룹은 포함된 리소스에 장애가 감지 되었을 경우 지정된 횟수 만큼 온라인을 시도합니다.
SingleNode Cluster
한개의 노드에서 실행 될 수 있는 리소스로 구성된 클러스터를 싱글 노드 클러스터라고 합니다. 싱글노드 클러스터는 페일오버 하지 않습니다.
싱글노드 클러스터에서는 오직 싱글노드 그룹만 지원합니다.
Cluster Attribute
Cluster attribute can be identified from clsuter Attributes view. From the group management view of MCCS web console, select the cluster, then select ‘Cluster Attributes’ tab located on the top of detailed information panel.
The values of gray colored are read only. They just contain and show the information of cluster state. The values of white colored are configurable by user definition. Below is description of some of them.
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
A single node cluster is a cluster of resources that can be run at a single node. A single node cluster does not failover.
A single node cluster only supports a single node group.
Cluster Attribute
Cluster attributes can be checked in the cluster attribute view.
In the group management view of the MCCS web console, select a cluster and press the 'Cluster Attribute value' tab on the right to view the detailed information.
The grey values are for reading only. These values represent the group status. The white colored values are defined by a user and they can be modified.
The below table explains some attributes.
[Figure] Cluster Attribute View
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 |
CLI
...
Use (mccluster
...
command)
MCCS 클러스터의 속성값을 수정 할 때 사용합니다. CLI를 사용하여 사용자가 원하는 속성 값을 수정 할 수 있습니다Used to modify the attribute values of an MCCS cluster. Using this CLI, a user can modify the desired attributes values.
| Info |
|---|
MCCS 는 설치 시 최초 사용자 계정으로 id 가 'admin' 암호가 'password'인 계정을 생성합니다. |
Syntax
| Code Block |
|---|
mccluster [-u userid -pw password] [-c clusterName] [-a attributeNameattribute] attrValattribute_value |
Options
| 옵션Option | 설명Description |
-h | 도움말을 출력합니다Display Help. |
| -u | 사용자 ID를 지정합니다Designate the user ID. |
| -pw | Enter the user password of the -u 옵션의 사용자 Password를 지정합니다option. |
-c | 명령을 실행하기 위해 접근할 클러스터를 지정합니다Designate a cluster to be accessed to run the command. |
-a | 수정하기 위한 속성값 이름을 지정합니다Designate the attribute name to be modified. |
Example
modify
testCluster의 클러스터 속성을 수정합니다Modify the cluster attributes of testCluster.
| Code Block |
|---|
mccluster -u admin -pw password -modify -c testCluster -a attribute attribute_value |
list
클러스터 상태를 출력합니다Display the cluster condition.
| Code Block |
|---|
mccluster -u admin -pw password -list |