Leaf States

Each leaf is in one of the following states:




In this state, a leaf is not part of the workspace.


This is the default, healthy state of a leaf. In the online state, the leaf is an active member of the distributed system and is either currently serving or ready to serve data to the aggregators.


The master aggregator periodically sends a heartbeat (ping) to all the nodes in a workspace to determine if they are responsive and online. A leaf enters the offline state if the master aggregator cannot reach it. The heartbeat frequency is based on typical network latencies and node responsiveness. It is set to a default of 150ms which has been empirically determined.

If the workspace is in redundancy 2 any partitions on the offline node will be failed over to the leaves pair. The master aggregator continues to ping offline nodes to detect when they should be moved into the attaching state.


Not online, and not available for read or write queries. A leaf in recovering state has been restarted and is replaying data back into memory.


In this state, the leaf is detached from the workspace.


A leaf transitions from offline to attaching when it is once again reachable by heartbeats.

The following diagram summarizes the leaf states and the transitions between them.

Last modified: June 15, 2023

Was this article helpful?