[SERVER-1404] Make moveChunk in d_migrate take min/max rather than query Created: 12/Jul/10  Updated: 12/Jul/16  Resolved: 15/Jul/10

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 1.5.5

Type: Task Priority: Major - P3
Reporter: Mathias Stearn Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-951 Shard Key compound key Closed
Participants:

 Description   

The rabbit hole goes pretty deep



 Comments   
Comment by auto [ 15/Jul/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: chunk migration totally its own logic now
should solve SERVER-1239 SERVER-1404
http://github.com/mongodb/mongo/commit/a446751e34d92fddc33fd1a63c5df8119d375cf8

Comment by auto [ 14/Jul/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: Commented out compound key test SERVER-951 SERVER-1404
http://github.com/mongodb/mongo/commit/64af09f8148f92ca1ee289bc0053b6fe8c4e470b

Comment by Mathias Stearn [ 14/Jul/10 ]

remove getFilter from chunk and shardkey. It is broken and only used for moveChunk

Generated at Thu Feb 08 02:56:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.