Loading...

XML

Word

Printable

JSON

Backwards Compatibility:
Fully Compatible
Backport Requested:

v6.0, v5.0
Sprint:
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
Case:
Linked BF Score:
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

is documented by

DOCS-15260 [SERVER] Investigate changes in SERVER-6491: Prevent dropping shard key index when alternative index doesn't exist

is duplicated by

SERVER-10309 Mongo should not allow removal of shard key index when the collection is not empty

SERVER-21688 Do not allow index for shard key to be dropped on sharded collections

is related to

SERVER-76973 Customers still able to drop shard key index in older server versions

related to

SERVER-64542 shardCollection no-op oplog can be written even when command ultimately fails

SERVER-67988 dropIndexes is not correctly serialized with other DDL operations in case of stepdowns

SERVER-64950 Use a named ErrorCode when asserting that you can't drop the last shard key index

SERVER-69492 check_orphans_are_deleted_helpers.js can safely assume the shard key index cannot be dropped

SERVER-67299 Prevent dropping shard key index when only remaining compatible index is multikey

(5 related to)

Participants:: Asya Kamsky, Garaudy Etienne, Gianfranco Palumbo, Githook User, Randolph Tan, Spencer Brody