{
  "schema_version": 2,
  "id": "operate/rs/clusters/remove-node",
  "title": "Remove a cluster node",
  "url": "https://redis.io/docs/latest/operate/rs/7.4/clusters/remove-node/",
  "summary": "Remove a node from your Redis Enterprise cluster.",
  "content": "You might want to remove a node from a Redis Enterprise cluster for one of the following reasons:\n\n- To [permanently remove a node](#permanently-remove-a-node) if you no longer need the extra capacity.\n- To [replace a faulty node](#replace-a-faulty-node) with a healthy node.\n- To [replace a healthy node](#replace-a-healthy-node) with a different node.\n\nYou can configure [email alerts from the cluster](https://redis.io/docs/latest/operate/rs/clusters/monitoring#cluster-alerts) to notify you of cluster changes, including when a node is removed.\n\n\u003e [!WARNING]\n\u003e Read through these explanations thoroughly before taking\n\u003e any action.\n\n## Permanently remove a node\n\nPermanently removing a node means you are decreasing cluster capacity.\nBefore trying to remove a node, make sure that the cluster has enough\ncapacity for all resources without that node, otherwise you cannot remove the node.\n\nIf there is not enough capacity in the cluster to facilitate removing\nthe node, you can either delete databases or add another node instead of\nthe one you would like to remove.\n\nDuring the removal process, the cluster migrates all resources from the\nnode being removed to other nodes in the cluster. In order to ensure\ndatabase connectivity, and database high availability (when replication\nis enabled), the cluster first creates replacement shards or endpoints\non one of the other nodes in the cluster, initiates failover as needed,\nand only then removes the node.\n\nIf a cluster has only two nodes (which is not recommended for production\ndeployments) and some databases have replication enabled, you cannot remove a node.\n\n## Replace a faulty node\n\nIf the cluster has a faulty node that you would like to replace, you\nonly need to add a new node to the cluster. The cluster recognizes the\nexistence of a faulty node and automatically replaces the faulty node\nwith the new node.\n\nFor guidelines, refer to [Replacing a faulty\nnode](https://redis.io/docs/latest/operate/rs/clusters/replace-node).\n\n## Replace a healthy node\n\nIf you would like to replace a healthy node with a different node, you\nmust first add the new node to the cluster, migrate all the resources\nfrom the node you would like to remove, and only then remove the node.\n\nFor further guidance, refer to [adding a new node to a\ncluster](https://redis.io/docs/latest/operate/rs/clusters/add-node).\n\nYou can migrate resources by using the `rladmin` command-line interface\n(CLI). For guidelines, refer to [`rladmin` command-line interface\n(CLI)](https://redis.io/docs/latest/operate/rs/references/cli-utilities/rladmin).\n\n\u003e [!NOTE]\n\u003e The [DNS records](https://redis.io/docs/latest/operate/rs/networking/cluster-dns) must be updated each time a node is added or replaced.\n\n## Remove a node\n\nTo remove a node using the Cluster Manager UI:\n\n1. If you are using the new Cluster Manager UI, switch to the legacy admin console.\n\n    ![Select switch to legacy admin console from the dropdown.](https://redis.io/docs/latest/images/rs/screenshots/switch-to-legacy-ui.png)\n\n1. On the **nodes** page, select the node you want to remove.\n\n1. Click **Remove** at the top of the **node** page.\n\n1. Confirm you want to **Remove** the node when prompted.\n\n1. Redis Enterprise Software examines the node and the cluster and takes the actions required\n    to remove the node.\n\n1. At any point, you can click the **Abort** button to stop the\n    process. When aborted, the current internal action is completed, and\n    then the process stops.\n    \n1. Once the process finishes, the node is no longer shown in\n    the UI.\n\nTo remove a node using the REST API, use [`POST /v1/nodes/\u003cnode_id\u003e/actions/remove`](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/nodes/actions#post-node-action).\n\nBy default, the remove node action completes after all resources migrate off the removed node. Node removal does not wait for migrated shards' persistence files to be created on the new nodes.\n\nTo change node removal to wait for the creation of new persistence files for all migrated shards, set `wait_for_persistence` to `true` in the request body or [update the cluster policy](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/cluster/policy#put-cluster-policy) `persistent_node_removal` to `true` to change the cluster's default behavior.\n\nFor example:\n\n```sh\nPOST https://\u003chostname\u003e:9443/v1/nodes/\u003cnode_id\u003e/actions/remove\n{\n    \"wait_for_persistence\": true\n}\n```\n\n\u003e [!NOTE]\n\u003e If you need to add a removed node back to the cluster,\n\u003e you must [uninstall](https://redis.io/docs/latest/operate/rs/installing-upgrading/uninstalling)\n\u003e and [reinstall](https://redis.io/docs/latest/operate/rs/installing-upgrading) the software on that node.\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-10-21T09:46:20-07:00"
}