Node Action Rules in MC

The table below summarizes when each node action is available for nodes in the primary subcluster or in a secondary subcluster.

For Eon Mode databases, MC supports actions for subcluster and node management:

  • In the cloud: On AWS and GCP.
  • On-premises: For Pure Storage FlashBlade.

For Enterprise Mode databases, MC supports these actions:

  • In the cloud on AWS: Add Node action, Add Instance action.
  • On-premises: Add Node action.

In the cloud on GCP, Enterprise Mode databases are not supported.

Node Action

Primary Subcluster

Secondary Subcluster

Start Node

Starts instance if needed.

Always allowed. Always allowed.

Stop Node 

Stops the instance on a cloud platform.

  • Allowed when K-safety is >=1. After the node is stopped, there must be 3 or more remaining UP nodes.
  • Not allowed when K-safety is 0.
  • Allowed when K-safety is >=1. After the node is stopped, there must be 3 or more remaining UP nodes.
  • Allowed when K-safety is 0.
Restart Node
  • Always allowed in the cloud.
  • Not available on premises.
  • Always allowed in the cloud.
  • Not available on premises.
The Remove Node action has been deleted from existing actions for all nodes. Use Scale Down subcluster instead.

When you start or stop a node on-premises, MC starts or stops the node in the database, but does not start or stop the Vertica host machine. The Restart Node action is not available for on-premises Eon Mode databases.

See Also

Starting, Stopping, and Restarting Nodes in MC