About PCE Supercluster Administration
This section explains how to perform common administration tasks for a PCE Supercluster.
Main Command | Option | Function | Node to run on |
|---|---|---|---|
| reset | Revert a PCE to a standalone state. | The affected node is being repaired to join the Supercluster. |
supercluster-assign-leader | Designate an existing Member PCE cluster to be a Supercluster Leader. | Any node | |
supercluster-drop | Removes a PCE cluster from a Supercluster. | Any node | |
supercluster-init-leader | Assign a PCE cluster as the Leader of your Supercluster. | Any node | |
supercluster-join | Joins a PCE cluster to a Supercluster. Note: Executing this command can take up to 30 minutes, depending on the number of PCEs in your Supercluster and the size of the PCE database. | On any Core node | |
supercluster-members | Displays all current active Supercluster PCEs, Members, and Leaders. | On any Core node or the Data0 node | |
supercluster-promote-replication | Establishes the database replication for the entire Supercluster. | On the Data node that is the database master | |
supercluster-restore | Restores a formerly failed Leader or Member to be restored to the Supercluster. This command can be run for a Leader or a Member. Note: Executing this command can take up to 1 hour, depending on the number of PCEs in the Supercluster and the size of the PCE database. | On any Core node | |
supercluster-upgrade-prepare | Prepares the cluster for database migration after a new version of the PCE software is installed during an upgrade. | Any node | |
supercluster-upgrade-rejoin | Rejoins a PCE to a Supercluster after a database migration during a software upgrade. | Any core node | |
| supercluster-data-restore | Restores a failed Leader from a database backup. | On one of the Data nodes only |
supercluster-quiesce | Pauses all the pending database replication, e.g., during a software upgrade. | On the Data node that is the database master |