[SERVER-15877] Give stepdown command some time to let secondaries catch up by default Created: 30/Oct/14 Updated: 11/Jul/16 Resolved: 30/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The stepDown command by default uses a 0 second wait-time, meaning if no secondaries are completely caught up in replication when the command grabs the global lock, it will fail. We should give secondaries some small amount of time (1 second?) to catch up after writes have been blocked before failing. |
| Comments |
| Comment by Githook User [ 30/Oct/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |