[SERVER-20789] moveChunk needs to send config optime when sending _recvChunkStart to destination shard Created: 06/Oct/15  Updated: 25/Jan/17  Resolved: 07/Oct/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding A (10/09/15)
Participants:
Linked BF Score: 0

 Description   

If the migration is the first sharding-aware operation that the recipient shard is participating in, then the _recvChunkStart command it receives will make it sharding-aware and load the chunk data for the chunk being migrated for the first time. If the collection was only recently created and sharded, there's a risk that it could load out of date data for the collection, causing it to see no chunks for this collection, which causes the migration to fail with an obscure "data transfer error". If the source shard included the config server optime when it sent _recvChunkStart, then there'd be no risk of the recipient shard reading stale data.



 Comments   
Comment by Githook User [ 07/Oct/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-20789 Use ShardConnection to send _recvChunkStart so that config server metadata is included
Branch: master
https://github.com/mongodb/mongo/commit/8d8c30d1a60fa75b09c672ef98e4665d49e412ff

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