[SERVER-22954] MigrationDestinationManager should not directly use MMAPv1 durable interface Created: 03/Mar/16 Updated: 12/Apr/17 Resolved: 24/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1, Sharding, Storage |
| Affects Version/s: | 3.3.2 |
| Fix Version/s: | 3.4.4, 3.5.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v3.4
|
||||
| Sprint: | Sharding 12 (04/01/16), Sharding 2017-03-27, Sharding 2017-04-17 | ||||
| Participants: | |||||
| Description |
|
The MigrationDestinationManager calls getDur().commitNow(), which is an MMAPv1-specific feature and requires cleanup. |
| Comments |
| Comment by Githook User [ 12/Apr/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: (cherry picked from commit 921f12c9aa005488ac93b672d74a63af51b93139) |
| Comment by Githook User [ 24/Mar/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Removes direct calls into MMAPV1 at migration flush time and replaces them As a side effect this also removes the last acquisition of the global S |
| Comment by Kaloian Manassiev [ 08/Mar/16 ] |
|
This call should not be there. I am going to remove it as part of the changes for parallel chunk migration. |
| Comment by Ian Whalen (Inactive) [ 07/Mar/16 ] |
|
kaloian.manassiev is this call needed by migrations? |