16.2.2 Node switching timing
Node switching is implemented at the following timing:
-
When Administration Agent or Management Server are down#1.
-
When the automatic restart frequency of the logical server exceeds the automatic restart frequency specified during system setup#2.
-
When a failure occurs in the node hardware or cluster software.
- #1
-
If automatic restart is specified for Administration Agent and Management Server, node switching is not executed during this time. For executing the node switching during this time, do not set up automatic restart for Administration Agent and Management Server.
- #2
-
You must specify the settings for switching the node (true) in the com.cosminexus.mngsvr.logical_server_abnormal_stop.exit key of the mserver.properties (Management Server environment setup file), when the logical server status is "abnormal termination" (the automatic restart frequency is exceeded or when 0 is specified as the automatic restart frequency and a failure is detected). For details on the settings for mserver.properties (Management Server environment setup file), see 16.3.3 Editing the setup file. If automatic restart is specified for Management Server, node switching is not executed during this time. For executing the node switching during this time, do not set up automatic restart for Management Server. If automatic restart is specified, use the mngautorun command to cancel the settings. For details about the mngautorun command, see mngautorun (Set up/canceling the set up of autostart and autorestart) in the uCosminexus Application Server Command Reference Guide.
In a configuration in which two or more executing nodes exist, do not specify true for the com.cosminexus.mngsvr.logical_server_abnormal_stop.exit key. If you do so, multiple systems of these executing nodes might start on the standby node.