...
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.
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 signal, Heartbeat signal is transferred at an interval 1/10 of this time. | INTEGER | 2000ms | O | |
HBPort | It is the heartbeat service 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 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. | 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 | |
| RuntimeExcuteTimeout | OS Command 연결 시간 제한을 입력합니다It limits running time, when executing OS commands, to a setting value. | INTEGER | 10sec | 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 |
| Info |
|---|
MCCS 는 사용자의 입력필드에 대한 입력값 제한 기능이 존재하며, 사용자가 잘못 입력한 데이터에 대해 자동 점검기능을 제공합니다. |
로그레벨은 다음과 같이 정의되어 있습니다.
...
잘못된 설정파일로 인한 MCCS 구동 실패등의 정보
| Info |
|---|
MCCS 의 로그를 시스템로그에 추가하려면 다음의 추가 설정이 필요합니다. /etc/rsyslog.conf 의 다음 두 라인의 주석을 해제 합니다.has function to limit input values against user's input field, and it provides function detects automatically data which is input wrong by user's mistake. |
The following table describes defined standard of log levels:
| Log Levels | Description |
|---|---|
DEBUG | Information on the following: detailed attributes related to groups, resources, or others, modifying detailed status, creating back-up files |
INFO | Information on the following: modifying the last value of groups, resources, or the others, or modifying the latest status |
WARN | Warning information on modifying status related to heartbeats or engines |
ERROR | Information on errors relatetd to the following: resource(FAULT status), execution of a batch script, location of a batch script, or etc. |
FATAL | Information on failure to run MCCS because of wrong configuration file |
| Info | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
To add MCCS log to a system log, do the following. On /ETC/RSYSLOG.CONF, uncomment two rows as follows: /ETC/RSYSLOG.CONF before uncommenting:
/ETC/RSYSLOG.CONF after uncommenting:
|
...
| Code Block |
|---|
mccluster [-u userid -pw password] [-c clusterName] [-a attribute] attribute_value |
Options
...
| Option | Description |
-h | Display Help. |
| -u | Enter the user account. |
| -pw | Enter the password. |
-c | Designate a cluster to be accessed to run the command. |
-a | Designate the attribute name to be modified. |
...