# ERR Slot 1234 is not assigned to any node

- **ID:** `redis/err-cluster-slot-unassigned`
- **Domain:** redis
- **Category:** config_error
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

In a Redis Cluster, a hash slot has not been assigned to any node, often due to incomplete cluster initialization, resharding failure, or node removal without reassigning slots.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Redis 7.0.14 | active | — | — |
| Redis 7.2.2 | active | — | — |
| redis-cli 7.2.2 | active | — | — |

## Workarounds

1. **Use redis-cli to fix the slot assignment: `redis-cli --cluster fix <any-node-ip>:6379`. This scans for unassigned slots and reassigns them automatically.** (90% success)
   ```
   Use redis-cli to fix the slot assignment: `redis-cli --cluster fix <any-node-ip>:6379`. This scans for unassigned slots and reassigns them automatically.
   ```
2. **Manually assign the slot to a node using: `redis-cli --cluster addslots <node-ip>:6379 1234` after ensuring the node has the slot range available.** (85% success)
   ```
   Manually assign the slot to a node using: `redis-cli --cluster addslots <node-ip>:6379 1234` after ensuring the node has the slot range available.
   ```
3. **If resharding was interrupted, resume it: `redis-cli --cluster reshard <source-node-ip>:6379 --from <source-node-id> --to <target-node-id> --slots 1234 --yes`** (80% success)
   ```
   If resharding was interrupted, resume it: `redis-cli --cluster reshard <source-node-ip>:6379 --from <source-node-id> --to <target-node-id> --slots 1234 --yes`
   ```

## Dead Ends

- **** — Slots are persisted in cluster configuration, not reset on restart. (99% fail)
- **** — New nodes need explicit slot assignment via resharding. (80% fail)