# 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](https://docs.hypertensor.org/network/consensus), `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](https://docs.hypertensor.org/network/subnet-node/classifications)) 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](https://docs.hypertensor.org/network/subnet-owner#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.