During the commit phase of the migration, the moveChunk command will set the chunk being migrated with a new major version and selects a random chunk of the current shard to have the same major version. This is done using replacement update so if a chunk that gets selected is a jumbo chunk, the flag will get cleared inadvertently.
Also uncomment this line in test after fixing:
https://github.com/mongodb/mongo/blob/27b771a1805871c1a87fab70d38e44b072b22c7f/jstests/sharding/jumbo1.js#L51
- is duplicated by
-
SERVER-26688 Chunks consisting of a single shard key value do not mark Jumbo when move/split fails
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-43524 Complete TODO listed in SERVER-26531
-
- Closed
-