Active Cluster Guide > Handling Active Cluster Errors > Setting a Timekeeper and Repairing Active Cluster Nodes
 
Setting a Timekeeper and Repairing Active Cluster Nodes
Having an effective way to recover nodes without restarting servers is essential. Recovering cluster nodes to a working state without restarting the TDV server helps maintain stable cluster environments. Regrouping the cluster attempts to establish connections with all the nodes in the cluster and set the timekeeper node. This can help if the:
Timekeeper is missing
Nodes are in different states such as CONNECTED, OPERATIONAL, and DISCONNECTED.
Cluster synchronization does not work.
You can attempt to regroup an Active Cluster node. When you regroup a node, Active Cluster resets all cluster connections for the node, and then the node rejoins the cluster and resynchronizes its metadata. Reachable nodes are regrouped to the cluster and have their connections recycled. Nodes that are shut down or unreachable are skipped.
If the node contains metadata changes that are incompatible with the rest of the cluster, it is not allowed to rejoin.
Regroup Using Manager
Regroup Using the cluster_util Script
Regroup Using the API