Details
-
Bug
-
Resolution: Incomplete
-
Major - P3
-
None
-
None
-
None
-
None
-
ALL
Description
I originally created this as a question at SERVER-36059, but that ticket was closed and after further investigation this seems to be a bug.
Steps to recreate
- Create a non sharded db where some of the keys that will eventual become "chunks" are around 512mb
- Configure the db to use a chunk size of 1024mb
- Start the sharding process
- See that the large chunks will not be moved and will be flagged as "jumbo"