[SERVER-29369] Unnecessary find of a chunk in _configsvrCommitChunkMigration Created: 25/May/17  Updated: 30/Oct/23  Resolved: 14/Jun/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.4.4, 3.5.7
Fix Version/s: 3.5.9

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Participants:

 Description   

The _configsvrCommitChunkMigration command, which is used to persist the new owner of a chunk after a migration performs one extra lookup of a chunk in order to verify that the collection epoch has not changed.

Given that we already find the highest chunk for a collection a little bit after, this call is not necessary.



 Comments   
Comment by Githook User [ 14/Jun/17 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-29369 Get rid of one extra find in _configsvrCommitChunkMigration
Branch: master
https://github.com/mongodb/mongo/commit/ca77c160790082f8efd64a98c586d4fd3f4f64b4

Comment by Kaloian Manassiev [ 25/May/17 ]

Rather, we can perform the check in the later call, when we have found the chunk with the highest version for the purposes of incrementing this value.

Comment by Andy Schwerin [ 25/May/17 ]

The call is unnecessary because the epoch check effectively happens in the later call?

Generated at Thu Feb 08 04:20:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.