[SERVER-48359] retry voteCommitIndexBuild on new primary if current primary is shutting down Created: 21/May/20 Updated: 29/Oct/23 Resolved: 22/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc7, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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.4
|
||||||||||||||||
| Sprint: | Execution Team 2020-06-01 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 14 | ||||||||||||||||
| Description |
|
When a secondary index build is ready to vote for commit readiness (using the voteCommitIndexBuild command in the IndexBuildsCoordinatorMongod::_checkVoteCommitIndexCmdSucceeded()), it may receive a ShutdownError if the remote primary is in the process of shutting down. This can lead to the secondary to stop the voting process prematurely. |
| Comments |
| Comment by Githook User [ 26/May/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry picked from commit 935fce45d2074ad9bc68fb9c5b05ed73e5fdc186) |
| Comment by Githook User [ 22/May/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Benety Goh [ 21/May/20 ] |
|
It is not clear that the presence of a shutdown error here necessarily implies a local shutdown condition. However, we can rely on this interruption check, introduced in |