[SERVER-25907] MigrationManager::CollectionMigrationsState doesn't need to hold onto the DistLockHandle value anymore Created: 31/Aug/16 Updated: 21/Sep/16 Resolved: 08/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding 2016-09-19 |
| Participants: |
| Description |
|
Since the MigrationManager is using clusterId as a lock session id, which is what DistLockHandle is, there is no longer a need for MigrationManager::CollectionMigrationsState to store this value – it will be a constant lockSessionID for every balancer instance: there's a _lockSessionID local variable in MigrationManager. Remove the MigrationManager::CollectionMigrationsState struct's distLockHandle variable, and clean up the MigrationManager code a bit because it no longer needs to handle it. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 31/Aug/16 ] |
|
Before going ahead with this ticket, should resolve this comment https://jira.mongodb.org/browse/SERVER-25905?focusedCommentId=1374009&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1374009 |