[SERVER-42353] indexbg_shutdown.js interrupts index build on secondary prematurely Created: 23/Jul/19 Updated: 29/Oct/23 Resolved: 23/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| 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 | ||||||||
| Sprint: | Execution Team 2019-07-29 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The JS test indexbg_shutdown.js obtains the opID from the db.currentOp() result in order to attempt to (unsuccessfully) abort the index build. Since the IndexBuildsCoordinator updates the db.currentOp() output before it disables interruptions on a secondary node, this creates a window during which it may be possible for the test to interrupt the index build prematurely. |
| Comments |
| Comment by Githook User [ 23/Jul/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |