{
  "schema_version": 2,
  "id": "commands/cluster-delslots",
  "title": "CLUSTER DELSLOTS",
  "url": "https://redis.io/docs/latest/commands/cluster-delslots/",
  "summary": "Sets hash slots as unbound for a node.",
  "since": "3.0.0",
  "tags": [
    "docs",
    "develop",
    "stack",
    "oss",
    "rs",
    "rc",
    "oss",
    "kubernetes",
    "clients"
  ],
  "last_updated": "2026-09-18T09:48:21+01:00",
  "page_type": "content",
  "content_hash": "b7c1edf10b65fe987477776c39c52bc6f3f1e96eb14952e7ff008d3a35ee7c2d",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "In Redis Cluster, each node keeps track of which master is serving\na particular hash slot.\n\nThe `CLUSTER DELSLOTS` command asks a particular Redis Cluster node to\nforget which master is serving the hash slots specified as arguments."
    },
    {
      "id": "required-arguments",
      "title": "Required arguments",
      "role": "content",
      "text": "<details open><summary><code>slot [slot ...]</code></summary>\n\nOne or more hash slots to unassign from the current node.\n\n</details>"
    },
    {
      "id": "examples",
      "title": "Examples",
      "role": "example",
      "text": "The following command removes the association for slots 5000 and\n5001 from the node receiving the command:\n\n    > CLUSTER DELSLOTS 5000 5001\n    OK"
    },
    {
      "id": "details",
      "title": "Details",
      "role": "content",
      "text": ""
    },
    {
      "id": "usage-in-redis-cluster",
      "title": "Usage in Redis Cluster",
      "role": "syntax",
      "text": "This command only works in cluster mode and may be useful for\ndebugging and in order to manually orchestrate a cluster configuration\nwhen a new cluster is created. It is currently not used by `redis-cli`,\nand mainly exists for API completeness."
    },
    {
      "id": "other-details",
      "title": "Other details",
      "role": "content",
      "text": "In the context of a node that has received a `CLUSTER DELSLOTS` command and\nhas consequently removed the associations for the passed hash slots,\nwe say those hash slots are *unbound*. Note that the existence of\nunbound hash slots occurs naturally when a node has not been\nconfigured to handle them (something that can be done with the\n[`CLUSTER ADDSLOTS`](https://redis.io/docs/latest/commands/cluster-addslots) command) and if it has not received any information about\nwho owns those hash slots (something that it can learn from heartbeat\nor update messages).\n\nIf a node with unbound hash slots receives a heartbeat packet from\nanother node that claims to be the owner of some of those hash\nslots, the association is established instantly. Moreover, if a\nheartbeat or update message is received with a configuration epoch\ngreater than the node's own, the association is re-established.\n\nHowever, note that:\n\n1. The command only works if all the specified slots are already\nassociated with some node.\n2. The command fails if the same slot is specified multiple times.\n3. As a side effect of the command execution, the node may go into\ndown state because not all hash slots are covered."
    },
    {
      "id": "redis-software-and-redis-cloud-compatibility",
      "title": "Redis Software and Redis Cloud compatibility",
      "role": "content",
      "text": "| Redis<br />Software | Redis<br />Cloud | <span style=\"min-width: 9em; display: table-cell\">Notes</span> |\n|:----------------------|:-----------------|:------|\n| <span title=\"Not supported\">&#x274c; Standard</span><br /><span title=\"Not supported\"><nobr>&#x274c; Active-Active</nobr></span> | <span title=\"Not supported\">&#x274c; Standard</span><br /><span title=\"Not supported\"><nobr>&#x274c; Active-Active</nobr></span> |  |"
    },
    {
      "id": "return-information",
      "title": "Return information",
      "role": "returns",
      "text": "**RESP2:**\n\n[Simple string reply](../../develop/reference/protocol-spec#simple-strings): `OK` if the command was successful. Otherwise an error is returned.\n\n**RESP3:**\n\n[Simple string reply](../../develop/reference/protocol-spec#simple-strings): `OK` if the command was successful. Otherwise an error is returned."
    }
  ],
  "examples": []
}