Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Execution EMEA Team 2023-08-07, Execution EMEA Team 2023-08-21
Linked BF Score:
135

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.

is depended on by

SERVER-69461 The behaviour of lock acquisitions differs depending on whether OpContext or Locker is used

Closed

is related to

SERVER-48062 Index build abort can race with stepdown

Closed

SERVER-48524 Acquire config.system.indexBuilds lock earlier and with collection lock

Closed

related to

SERVER-83168 Make index build uninterruptible after commit

Closed

Assignee:: Yujin Kang Park

Reporter:: Yujin Kang Park

Participants:: Githook User, Yujin Kang Park

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: Jul 21 2023 11:10:56 AM UTC

Updated:: Nov 13 2023 02:54:34 PM UTC

Resolved:: Aug 10 2023 11:30:17 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates