[SERVER-22997] Unify checking for stale sharding version and waiting for migration critical section Created: 07/Mar/16  Updated: 14/Apr/16  Resolved: 17/Mar/16

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
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-22359 Move MigrationSource Manager under co... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 11 (03/11/16), Sharding 12 (04/01/16)
Participants:

 Description   

Currently checking for shard version mismatch is done in an ad-hoc manner and so is the waiting for the migration critical section to complete on the donor shard.

We should unify all these places.



 Comments   
Comment by Githook User [ 17/Mar/16 ]

Author:

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

Message: SERVER-22997 Unify wait for migrate critical section and metadata refresh

This change gets rid of commands explicitly waiting for critical section
establishment and instead makes all operations when they encounter stale
version to install a wait object on the OperationContext, which can be
used to wait for critical section outside of lock. It also makes refresh
to happen outside of lock.
Branch: master
https://github.com/mongodb/mongo/commit/ee5fbdd8540d93d2e0d6fa19ba9a5595bb1829cb

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