# 3.3.7 Cluster Formation

A cluster is represented by a group of servers that have a common leader. A cluster is a virtual non-existent (empty) node that describes a group of a server as one whole.

* Forming a cluster is only possible within the conditions specified by the topology (a node that joins the network receives a “license” to open its cluster
* Each cluster has a leader who collects data based on voting results. After a given number of rounds (also determined by the topology processor), a change of leader occurs. This leads to the change of all permalinks – those inside the cluster, and those leading inside it and outside as well.
* The change of permalinks is one of the transactions of the topological processor and is written inside the ledger.
* A cluster can have a limit on its width (number of nodes inside it) and depth (the number of other clusters connected to it by permalinks)
* In case of loss of connection on the existing permalinks, the remounting operation is provided. It performs the regrouping of nodes in the absence of communication with the “parent cluster.”


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dgtnetwork.gitbook.io/dgt-docs/3.-dgt-architecture/3.3-network-architecture/3.3.7-cluster-formation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.