-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding 2021-03-22
-
153
-
1
It is technically possible for a user to manually create a "system.resharding." collection that isn't sharded. The invariants in ReshardingOpObserver::onInserts() and ReshardingOpObserver::onUpdate() should be changed to a uassert(ErrorCodes::NamespaceNotSharded, ..., metadata && metadata->isSharded()) to avoid crashing the server in such a situation.
- causes
-
SERVER-59023 Resharding can fail with NamespaceNotSharded following a primary failover on a recipient shard
- Closed
- is caused by
-
SERVER-52639 Fail resharding operation if new shard key includes array
- Closed
- related to
-
SERVER-60094 ReshardingOplogApplicationRules does not version all writes
- Closed