[SERVER-15674] Auto split of low top chunk does not move it to appropriate shard node Created: 15/Oct/14  Updated: 11/Jul/16  Resolved: 05/Dec/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.7.7
Fix Version/s: 2.8.0-rc3

Type: Bug Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-15831 Enhanced top chunk auto split tests Closed
Tested
Operating System: ALL
Steps To Reproduce:

In a 4 node sharded cluster, configure as follows:

  • Pre-split collection such that it is imbalanced (set to a large number of chunks on the nodes that it will be moved from).
  • shard0 - low "top chunk "Tag "NYC" 10 chunks -infinity -> 0
  • shard1 - middle chunks Tag "SF" 10 chunks 0 -> 500
  • shard2 - high "top chunk" Tag "NYC" 2 chunks 1000 -> infinity
  • shard3 - middle chunks Tag "SF" 1 chunk 500 -> 1000

Insert into low "top chunk" to create a new chunk
The new low "top chunk" should be created and reside on shard2
The previous low "top chunk" should still reside on shard0

Participants:

 Description   

"Top chunks" are the special chunks with MinKey or MaxKey in their range. A low "top chunk" is the chunk with the MinKey. When an auto split is required on a top chunk the auto split should perform the split and move the new top chunk to another node if required.



 Comments   
Comment by Githook User [ 05/Dec/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-15674 Auto split of low top chunk does not move it to appropriate shard node
Branch: master
https://github.com/mongodb/mongo/commit/efe02e71561d2ca9ebd4419734f235603c94a9da

Generated at Thu Feb 08 03:38:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.