{
  "schema_version": 2,
  "id": "commands/cluster-delslotsrange",
  "title": "CLUSTER DELSLOTSRANGE",
  "url": "https://redis.io/docs/latest/commands/cluster-delslotsrange/",
  "summary": "Sets hash slot ranges as unbound for a node.",
  "since": "7.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": "98d76b4bd413d461c35208f6bc79b070c44c2459d3afe3a710d0ecd13ac991da",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "The `CLUSTER DELSLOTSRANGE` command is similar to the [`CLUSTER DELSLOTS`](https://redis.io/docs/latest/commands/cluster-delslots) command in that they both remove hash slots from the node.\nThe difference is that [`CLUSTER DELSLOTS`](https://redis.io/docs/latest/commands/cluster-delslots) takes a list of hash slots to remove from the node, while `CLUSTER DELSLOTSRANGE` takes a list of slot ranges (specified by start and end slots) to remove from the node."
    },
    {
      "id": "required-arguments",
      "title": "Required arguments",
      "role": "content",
      "text": "<details open><summary><code>start-slot end-slot [start-slot end-slot ...]</code></summary>\n\nOne or more inclusive ranges of hash slots to unassign from the current node.\n\n</details>"
    },
    {
      "id": "examples",
      "title": "Examples",
      "role": "example",
      "text": "To remove slots 1 2 3 4 5 from the node, the [`CLUSTER DELSLOTS`](https://redis.io/docs/latest/commands/cluster-delslots) command is:\n\n    > CLUSTER DELSLOTS 1 2 3 4 5\n    OK\n\nThe same operation can be completed with the following `CLUSTER DELSLOTSRANGE` command:\n\n    > CLUSTER DELSLOTSRANGE 1 5\n    OK\n\nHowever, note that:\n\n1. The command only works if all the specified slots are already associated with the 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 *down* state because not all hash slots are covered."
    },
    {
      "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": "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": []
}