-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.0.6, 2.1.2, 2.4.10
-
Component/s: Index Maintenance, Sharding
-
Fully Compatible
-
v6.0, v5.0
-
Sharding 2022-02-21, Sharding 2022-03-07, Sharding NYC 2022-03-21, Sharding NYC 2022-04-04, Sharding NYC 2022-04-18, Sharding 2022-05-02
-
(copied to CRM)
-
135
This leaves you without an index on the shard key, which can have big performance implications, especially on migrations.
- causes
-
SERVER-66264 shardsvrDropIndex should use timeseries namespace in the shardVersionRetry loop
- Closed
- is duplicated by
-
SERVER-10309 Mongo should not allow removal of shard key index when the collection is not empty
- Closed
-
SERVER-21688 Do not allow index for shard key to be dropped on sharded collections
- Closed
- is related to
-
SERVER-76973 Customers still able to drop shard key index in older server versions
- Closed
- related to
-
SERVER-64542 shardCollection no-op oplog can be written even when command ultimately fails
- Closed
-
SERVER-67988 dropIndexes is not correctly serialized with other DDL operations in case of stepdowns
- Closed
-
SERVER-64950 Use a named ErrorCode when asserting that you can't drop the last shard key index
- Closed
-
SERVER-69492 check_orphans_are_deleted_helpers.js can safely assume the shard key index cannot be dropped
- Closed
-
SERVER-67299 Prevent dropping shard key index when only remaining compatible index is multikey
- Closed