[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: |
|
||||||||||||||||||||||||
| 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: This ensures that we will have assertions in place for the correct locks |
| 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: This name is more appropriate now, because we will be attaching more |
| 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: Use the CollectionShardingState for notifications from the oplog observer Also gets rid of the threading through of the fromMigrate flags down to |
| 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: |