When a classic (local disk-based) cluster instance has a private endpoint or has Global Distributed Cache enabled, you cannot change shard specifications and the number of shards at the same time. Each configuration change must target one dimension only.
| Operation | Supported |
|---|---|
| Change shard specifications only | Yes |
| Change the number of shards only | Yes |
| Change both at the same time | No |
Solution
Choose an approach based on whether you need to keep the private endpoint or Global Distributed Cache.
Keep the private endpoint or Global Distributed Cache
Change either shard specifications or the number of shards per operation — not both.
Starting from an instance with 4 shards × 2 GB per shard (8 GB total):
Change shard specifications only
| Direction | Result |
|---|---|
| Upgrade | 4 shards × 4 GB per shard = 16 GB |
| Downgrade | 4 shards × 1 GB per shard = 4 GB |
Change the number of shards only
The new shard count must be twice or half the original number.
| Direction | Result |
|---|---|
| Double | 8 shards × 2 GB per shard = 16 GB |
| Halve | 2 shards × 2 GB per shard = 4 GB |
Release the private endpoint or distributed instance
If you no longer need the private endpoint or Global Distributed Cache, release the relevant resource. After the release, the restriction no longer applies and you can change shard specifications and the number of shards at the same time.
-
To release a private endpoint, see Release a private endpoint.
-
To release a distributed instance, see Release a distributed instance.