[SERVER-79176] Index build _completeExternalAbort should be resilient to interrupts Created: 21/Jul/23  Updated: 13/Nov/23  Resolved: 10/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.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:
Depends
is depended on by SERVER-69461 The behaviour of lock acquisitions di... Closed
Related
related to SERVER-83168 Make index build uninterruptible afte... Closed
is related to SERVER-48062 Index build abort can race with stepdown Closed
is related to SERVER-48524 Acquire config.system.indexBuilds loc... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution EMEA Team 2023-08-07, Execution EMEA Team 2023-08-21
Participants:
Linked BF Score: 135

 Description   

Although there are no interrupt points called directly within _completeExternalAbort, some OpObservers might happen to check for interrupts. For instance, this happened during SERVER-69461, which made some sharding acquisitions interruptible and triggered fassert 4656011.



 Comments   
Comment by Githook User [ 10/Aug/23 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-79176 Make index build abort uninterruptible
Branch: master
https://github.com/mongodb/mongo/commit/3e2769c569addabbefe0b45bdb9998112196e352

Generated at Thu Feb 08 06:40:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.