[SERVER-17760] moveChunk, mergeChunk, splitChunk commands should use catalog manager to connect to config servers Created: 26/Mar/15  Updated: 19/Sep/15  Resolved: 23/Apr/15

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Daniel Alabi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-17759 moveChunk should use catalog manager ... Closed
is duplicated by SERVER-18123 mergeChunk should use catalog manager... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 1 04/03/15, Sharding 2 04/24/15
Participants:

 Description   

Tracks any micro-design and coding work needed to move the split chunk function to the catalog manager.



 Comments   
Comment by Githook User [ 20/Apr/15 ]

Author:

{u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}

Message: SERVER-17760 moveChunk, mergeChunk, splitChunk commands should use catalog manager for applyOps
Branch: master
https://github.com/mongodb/mongo/commit/8e5b16fe0d64d587e0741dab7cabe64b0a818e51

Comment by Githook User [ 17/Apr/15 ]

Author:

{u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}

Message: SERVER-17760 shardId no longer used by splitChunk and moveChunk commands

In mongods <= 2.6, we use shardId to get the current metadata
information for the current chunk. Now, we use cached CollectionMetadata.
Branch: master
https://github.com/mongodb/mongo/commit/ea32e99a4e06930b2cae7b03882e3fda3333934b

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