Details
-
Task
-
Resolution: Done
-
Critical - P2
-
None
-
None
Description
We should update
https://www.mongodb.com/docs/manual/core/sharding-refine-a-shard-key/
and
to more explicitly state that you cannot modify the index type as part of this operation. In some versions this will succeed (SERVER-69220 will block it), but introduce sharding metadata inconsistencies.
For example, users should not refine from {a:1} to {a:"hashed",b:1}. As this would make the routing table not match the physical location of the documents.
Attachments
Issue Links
- related to
-
SERVER-69220 refineCollectionShardKey permits toggling current shard key fields between range-based and hashed, leading to data inconsistency
-
- Closed
-