[SERVER-30719] Fix dbCheck behavior during stepdown Created: 17/Aug/17 Updated: 30/Oct/23 Resolved: 23/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.13 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Kuehne | Assignee: | Ian Kuehne |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Storage 2017-08-21, Storage 2017-09-11 | ||||||||
| Participants: | |||||||||
| Description |
|
dbCheck currently fails on an fassert if stepdown occurs while it is running. It should silently fail per the design doc. |
| Comments |
| Comment by Ramon Fernandez Marina [ 24/Aug/17 ] |
|
Author: {'username': u'ikuehne', 'name': u'Ian Kuehne', 'email': u'ian.kuehne@mongodb.com'}Message: |
| Comment by Ian Kuehne [ 22/Aug/17 ] |
|
Takes a global IX lock as a workaround for |