activate_cluster.py

The activate_cluster.py script makes the specified cluster the HA ACTIVE cluster. Its purpose is to switch the state of the STANDBY cluster to an ACTIVE state.

The target cluster must be running in order for the activate_cluster.py script to activate it. If it is not, the script returns an error and exits. If the target cluster is already in an ACTIVE state, it does nothing and returns. If the target cluster is in a STANDBY state, before doing the switchover operation, it checks the following configurations to make certain the cluster is ready to be activated.
  • Only two engines are running in the domain.
    Important: If your production environment has three running engines, you cannot switch the active and standby states of two clusters. You must first stop the engine that is not part of the switchover operation.
  • All servers in the standby cluster are in an active state and not in a sync state.
  • The standby cluster is in the standby state and is synchronized with the active cluster.
  • Both engines are running the same version of MATRIXX.
If any of these checks fail, the switchover is disallowed and the script exits with a return code of 1 (failure). If all checks pass, the script issues a switchover command on the active cluster by running the cluster_mgr_cli.py script. If the switchover command fails, the script exits with a return code of 1. Otherwise, the script verifies that the specified cluster is in an active state before it exits with a return code of 0 (success).
Note: The activate_engine.py script only activates the processing cluster during a switchover operation. The script does not influence the state of the publishing cluster because this cluster is used only for post-processing operations. This behavior is as designed.
  • Only two engines are running in the domain.
    Important: If your production environment has three running engines, you cannot switch the active and standby states of two clusters. You must first stop the engine that is not part of the switchover operation.
  • All servers in the standby cluster are in an active state and not in a sync state.
  • The standby cluster is in the standby state and is synchronized with the active cluster.
  • Both engines are running the same version of MATRIXX.
If any of these checks fail, the switchover is disallowed and the script exits with a return code of 1 (failure). If all checks pass, the script issues a switchover command on the active cluster by running the cluster_mgr_cli.py script. If the switchover command fails, the script exits with a return code of 1. Otherwise, the script verifies that the specified cluster is in an active state before it exits with a return code of 0 (success).
Note: The activate_engine.py script only activates the processing cluster during a switchover operation. The script does not influence the state of the publishing cluster because this cluster is used only for post-processing operations. This behavior is as designed.

Syntax

activate_cluster.py [-h] [-d] [--debug_config_file_parsing] [--debug_function_calls] [--debug_output_formatting] [--debug_threading_code] -e engineId [-w 0|1 -t seconds] [--plain] [-s] [-u username] [--ssh_debug]

Options

Make the Local Cluster ACTIVE

activate_cluster.py

Make Cluster ID 2:1 ACTIVE

activate_cluster.py -c 2:1