[SERVER-74360] vote_abort_index_build.js sporadic failure due to secondary with 0 votes Created: 24/Feb/23 Updated: 29/Oct/23 Resolved: 28/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yujin Kang Park | Assignee: | Yujin Kang Park |
| 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 | ||||
| Sprint: | Execution Team 2023-03-06 | ||||
| Participants: | |||||
| Linked BF Score: | 35 | ||||
| Description |
|
vote_abort_index_build.js relies on majority write concern wait, but secondary node is configured with 'votes: 0', meaning it does not participate in the write concern. This results in the test sporadically failing because the secondary has not yet applied the abort entry when the test expects that to be the case. |
| Comments |
| Comment by Githook User [ 28/Feb/23 ] |
|
Author: {'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}Message: |