[SERVER-80598] Fix index_secondary_wait_for_abort.js assertIndexes race Created: 31/Aug/23 Updated: 29/Oct/23 Resolved: 05/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.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 EMEA Team 2023-09-04, Execution EMEA Team 2023-09-18 | ||||
| Participants: | |||||
| Linked BF Score: | 35 | ||||
| Description |
|
The test originally relied on the primary detecting an index inconsistency and aborting the index build from within the builder thread and replicating to the secondary. Which is why waitForIndexBuildToStop + awaitForReplication + assertIndexes guaranteed the assert on secondary would work. After graceful index builds, the secondary initiates an abort command on the primary, the index builder thread is killed, and the abort is external. So the above does not apply anymore. |
| Comments |
| Comment by Githook User [ 04/Sep/23 ] |
|
Author: {'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}Message: |