-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
Cluster Scalability 2024-5-27
The last step of removeShard in 8.1+ is updating the "hasTwoOrMoreShards" cluster parameter if the number of shards goes from 2 back to 1. If there is an interrupt before that step, the "hasTwoOrMoreShards" cluster parameter would be left as true even if there is a retry because the retry would fail with ShardNotFound here and never get to the cluster parameter update step.
- is caused by
-
SERVER-81974 Update hasTwoOrMoreShards cluster parameter when second shard is removed from the cluster
- Closed
- related to
-
SERVER-90189 'hasTwoOrMoreShards' cluster parameter can be incorrect if addShard/removeShard is interrupted and not retried
- Open