[SERVER-24866] Balancer should be able to recover its state after CSRS primary stepdown/crash Created: 01/Jul/16  Updated: 19/Nov/16  Resolved: 14/Sep/16

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
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-22935 Add JS/client function to retry moveC... Closed
Gantt Dependency
has to be done before SERVER-26099 Interrupt MigrationManager::finishRec... Closed
has to be done after SERVER-25703 Enable dist lock unlock by sessionId ... Closed
Related
is related to SERVER-24853 Refactor Balancer code to use Migrati... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 17 (07/15/16), Sharding 18 (08/05/16), Sharding 2016-08-29, Sharding 2016-09-19
Participants:

 Description   

Write a "recovery" method on the MigrationManager for the case where it steps down (with a bunch of migrations going on) and then starts up again on a another primary. In this case the new MigrationManager will have to "inherit" the active migrations and wait for them to complete before doing another round.

*Write a JS test to test this, including querying the config.migrations collection at points to check it is correct.



 Comments   
Comment by Githook User [ 14/Sep/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-24866 Balancer recovery
Branch: master
https://github.com/mongodb/mongo/commit/3596a4fb09b31c955d95fbe17db0492589c96f03

Comment by Dianna Hohensee (Inactive) [ 31/Aug/16 ]

Code review url: https://mongodbcr.appspot.com/97000001

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