Active Cluster Guide > Handling Active Cluster Errors > Troubleshooting > The Timekeeper Cluster Node Fails or Is Taken Offline
 
The Timekeeper Cluster Node Fails or Is Taken Offline
If the timekeeper cluster node becomes unavailable for any reason, another TDV Server assumes timekeeper responsibilities automatically. You can see which cluster node is the timekeeper in the Timekeeper column on the CLUSTER MANAGEMENT page in Manager.
The timekeeper role assignment can change based on circumstances:
If the original timekeeper was disconnected due to a failure but not shut down, it resumes the timekeeper role after it successfully reconnects and resynchronizes. If the cluster is partitioned into subgroups as a result of the failure, each subgroup gets its own timekeeper. See Nodes Have Been Partitioned into Subgroups. The original timekeeper remains timekeeper for its subgroup and resumes the timekeeper role for the entire cluster when the subgroups are merged.
If the original timekeeper node is being repaired, the next node that joined the cluster becomes the timekeeper. The new timekeeper keeps its role as timekeeper even after the old timekeeper node is repaired.
If the original timekeeper fails to send a heartbeat to the cluster group, the next node that joined the cluster becomes the new timekeeper.