[SERVER-46218] Race between removal and shutdown in arbiter Created: 18/Feb/20 Updated: 29/Oct/23 Resolved: 20/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.4, 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | Repl 2020-02-24 | ||||
| Participants: | |||||
| Description |
|
If an arbiter is shut down soon after it is removed from the replica set by a reconfig, the arbiter crashes and logs:
The sequence is on the arbiter is:
I can only reproduce this with an arbiter, not a data node, not sure why. Proposed fix: KeysCollectionManager::PeriodicRunner::setFunc catches and logs shutdown errors. |
| Comments |
| Comment by Githook User [ 21/Feb/20 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}Message: If an arbiter is shut down soon after it is removed from the replica set (cherry picked from commit 32f47846d78a4fdae9564b7ebb442d53e737d845) |
| Comment by Githook User [ 20/Feb/20 ] |
|
Author: {'username': 'ajdavis', 'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com'}Message: If an arbiter is shut down soon after it is removed from the replica set |
| Comment by A. Jesse Jiryu Davis [ 18/Feb/20 ] |
|
The bug was apparently introduced between 4.2.1 and 4.2.2, I haven't bisected it to a specific commit yet. This fix should be backported to 4.2. I'm putting this in the Safe Replica Set Reconfig epic since it's blocking testing for that project. |