[SERVER-22359] Move MigrationSource Manager under collection lock Created: 29/Jan/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: Crystal Horn Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-22972 Some usages of OldClientContext refer... Closed
depends on SERVER-23015 Do not do shard version checking on t... Closed
depends on SERVER-22997 Unify checking for stale sharding ver... Closed
Duplicate
is duplicated by SERVER-19662 Assert that mongod never refreshes th... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 10 (02/19/16), Sharding 11 (03/11/16), Sharding 12 (04/01/16)
Participants:

 Description   

This task is to make the migration source and destination managers owned by the collection and protected by collection lock.



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

Author:

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

Message: SERVER-22359 Move ensureShardVersionOkOrThrow to CollectionShardingState

This ensures that we will have assertions in place for the correct locks
being held.
Branch: master
https://github.com/mongodb/mongo/commit/44d8a4dd0f8f27b72e2040e2bde74c552739eb23

Comment by Githook User [ 09/Mar/16 ]

Author:

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

Message: SERVER-22359 Rename OperationShardVersion to OperationShardingState

This name is more appropriate now, because we will be attaching more
metadata to it such as the critical section wait handle, which is
necessary for parallel migrations.
Branch: master
https://github.com/mongodb/mongo/commit/6c0d7a6635d93d3f82cf027d45a34a48c428234a

Comment by Githook User [ 07/Mar/16 ]

Author:

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

Message: SERVER-22359 Move op observer hooks to CollectionShardingState

Use the CollectionShardingState for notifications from the oplog observer
instead of calling into the global ShardingState object.

Also gets rid of the threading through of the fromMigrate flags down to
the sharding state.
Branch: master
https://github.com/mongodb/mongo/commit/e4bd8cef2b34b96f07986d8523333dd3c6b29f1a

Comment by Githook User [ 03/Mar/16 ]

Author:

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

Message: SERVER-22359 Introduce per collection sharding state
Branch: master
https://github.com/mongodb/mongo/commit/7e477bdff837da38f49c2e7fb503b09a2407f45e

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