> For the complete documentation index, see [llms.txt](https://docs.hypertensor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypertensor.org/build-a-subnet/consensus/removing-nodes.md).

# Removing Nodes

When subnet node slots become full, there must be a way to remove nodes that are the lowest performing in the queue.

#### There are two methods to remove nodes

1. **Leaving a node absent from the consensus data**
   1. When a node is absent from the consensus data, i.e., the scores a validator submits, all absent nodes will have their reputation decreased, which will ultimately have them removed once it goes below the minimum reputation set by the subnet owner.
2. **Utilizing the queue management system**
   1. When a validator submits consensus data, there are two [optional inputs](/network/consensus.md), `prioritize_queue_node_id` and `remove_queue_node_id`. By using `remove_queue_node_id`, the subnet can come to a consensus to remove a node in the queue.
   2. Registered (see [classifications](/network/subnet-node/classifications.md)) nodes that are in the queue can only be activated once a slot is available. If a registered node in the queue is evaluated in the subnet to be higher-performing than a currently active subnet node, the node that is lower-performing should be left out of the consensus data for its reputation to go below the minimum allowable reputation until it's removed (see [minimum reputation](/network/subnet-owner.md#update-minimum-subnet-node-reputation) in the subnet owner section). This will create room by opening a slot for one of the registered subnet nodes that are in the queue to become activated to take their place.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.hypertensor.org/build-a-subnet/consensus/removing-nodes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.