...
Node attribute can be identified from NodeAttributes view of MCCS console.
From the node management view of MCCS console, select node, then select the ‘Node Attributes’ tab located on right top of detailed information panel.
The values of gray colored are for read only. They just contain and show the information of node state. The values of white colored are configurable by user definition. Below is description of some of them.
[Figure] Node Attribute View
...
Attribute | Description | Type | Default | Edit | Note | |||||||||||||||
| BootDiskMonitor | It indicates whether or not the failure of the boot disk is under monitoring. | BOOLEAN | false | O | ||||||||||||||||
| BootDiskMonitorInterval | It indicates the time interval until starting the next monitoring. | INTEGER | 10 | O | ||||||||||||||||
| BootDiskMonitorRetryLimit | It sets the number of times to retry if the failure of the boot disk I/O test occurs. | INTEGER | 0 | O | ||||||||||||||||
| BootMode | It is value that indicate whether or not to been started according to the bootMode value setting when MCCS service starts. | BOOLEAN | X | |||||||||||||||||
| ExpirationDate | It shows expiration date of license key. | STRING | X | |||||||||||||||||
| HostID | It shows host ID of the node. | STRING | X | |||||||||||||||||
| IsolationTestAddresses | It enters the IP address to test Isolation at split-brain event. It is recommended the reliable IP address.
| IP ADDRESS | O | |||||||||||||||||
| LicenseType | It shows license type of the node. | STRING | X | |||||||||||||||||
NodeName | It show the name of the node. You can use an actual host name or nickname. | NAME |
| X | ||||||||||||||||
NodeState | It shows the state of the node. | STRING |
| X | ||||||||||||||||
PrimaryHB1 | It shows an IP address of the Primary Heartbeat1 defined in the MCCS server. | IP ADDRESS |
| X | ||||||||||||||||
| PrimaryHB1Status | It shows state of primary heartbeat1. | IP ADDRESS | X | |||||||||||||||||
PrimaryHB2 | It shows an IP address of the Primary Heartbeat2 defined in the MCCS server. | IP ADDRESS |
| X | ||||||||||||||||
| PrimaryHB2Status | It shows state of primary heartbeat2. | IP ADDRESS | X | |||||||||||||||||
SecondaryHB | It shows an IP address of the Secondary Heartbeat defined in the MCCS server. | IP ADDRESS |
| X | ||||||||||||||||
| SecondaryHBStatus | It shows state of secondary heartbeat. | IP ADDRESS | X | BootDiskMonitor | 부트 디스크 장애 모니터링 유무를 나타냅니다. | BOOLEAN | false | O | BootDiskMonitorInterval | 부트 디스크 모니터 할 때, 다음 모니터링까지의 시간 간격을 나타냅니다. | INTEGER | 10 | O | BootDiskMonitorRetryLimit | 부트 디스크 I/O 테스트 실패할 경우 재시도 횟수를 지정한다. | INTEGER | 0 | O |
| Info |
|---|
| Info |
MCCS 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. |
How MCCS Works
MCCS connects nodes as a cluster through heartbeat connection.
Action of the cluster is decided by the state and role of the node, and node states are decided not only by the system state but also the state of heartbeat connection.
Following are node states for Cluster Mode.
Node states of the Cluster Mode
| State | Description |
|---|---|
| EXITED | This is a state where MCCS engine is terminated. |
| INITING | This is a state before configuring the heartbeat after starting the engine. This is initial state before both nodes communicate each other through heartbeat network and collect mutual status of node state after MCCS engine is started. This state is normally changed to the LOCAL_BUILD or REMOTE_BUILD state, but if there is a problem with the configuration or physical environment, it remains in the INITING state, or is automatically terminated to the EXITED state. |
| LOCAL_BUILD | When every node in the cluster is in the INITING state, the node with the highest priority at establishing of heartbeat communication is changed to the LOCAL_BUILD state, and the node in this state forms a cluster database from the local configuration file(%MCCS_HOME%\config\main.json). Only one node within the cluster goes through this state to the RUNNING state, and other nodes undergo the REMOTE_BUILD state that receives information from that node. |
| REMOTE_BUILD | When a node in the INITING state detects a node in the RUNNING state through heartbeat communication, it establishes by downloading the configuration. |
| REMOTE_BUILD | This is the state when establishing a configuration database through the LOCAL_BUILD or REMOTE_BUILD is completed, and starts agents and group administrators of all the resources defined at this state. |
| FAULTED | When all the heartbeats with the node in the RUNNING state are disconnected, the node is FAULTED. |
...
- In the web console, select the node management view and select the node --> right click --> select 'Change Nodename' from menu.
[Figure] Node Name Change Selected - The screen will prompt you to enter the new node name to change.
Enter the node name to change.
[Figure] New Node Name Input - In the node management view, you can check the newly changed node name.
...
| Code Block |
|---|
mcnode [-u userid -pw password] [-ip node_ip_address] -command [-a attribute] [-l license] [-p download_path] |
Options
| Option | Description |
|---|---|
-h | Display Help. |
| -u | Enter the user account. |
| -pw | Enter the password. |
-n | It defines the node to access to execute command. If omitted, it will access to execute command for local node. |
-a | If the [modify] command is used, set the attribute and the attribute values to change. |
-path | Designate the path for downloading the support file. If you do not enter the path, it will be downloaded to 'user.home'. |
| -l | Enter the license value to be entered for the designated node. |
...