Terminating Subclusters in MC
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.
In Enterprise Mode, subclusters are not supported.
In the Cloud
The Terminate action for subclusters is available for Eon Mode databases only in the cloud.
You can terminate any subcluster that will not cause the database to go down. You can terminate:
- Any secondary subcluster.
- A primary subcluster, provided that:
- There is at least one other primary subcluster in the database.
- The other primary subcluster is at least one node larger than the one you want to terminate.
Terminate a Subcluster
- On the Manage > Subclusters tab, click Terminate immediately above the target subcluster.
- In the Terminate Subcluster window, click the check box to confirm you want to delete the chosen subcluster and terminate its instances.
-
Click Terminate Subcluster.
MC displays a progress window that shows the steps it is executing to terminate the subcluster.
- When all the steps are checked, click Close.
On-Premises
The Terminate action for subclusters is not available for Eon Mode on-premises. You can stop a subcluster on-premises, provided doing so will not bring down the database. You cannot terminate a subcluster on-premises, because terminating a subcluster stops the nodes and then terminates the cloud instances those nodes reside on. MC cannot terminate on-premises Vertica host machines.
To free up some of the Vertica host machines in an on-premises subcluster, scale down the subcluster.