Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Storage Execution NAMER
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Execution NAMR Team 2023-09-04
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Index builds handle WriteConflicts while aborting, and it is not expected that the operation fails as it means the index build ended up partially teared down, triggering this fassert.

The initial sync fuzzer, and potentially other tests, enable the skipWriteConflictRetries and can trigger the fassert.

is related to

SERVER-49396 Only activate skipWriteConflictRetries failpoint for user connections

Closed

SERVER-40062 Add failpoint to skip doing retries on WriteConflictExceptions

Closed

SERVER-73292 Add internal voteAbortIndexBuild command

Closed

SERVER-40103 Improve retry behavior of non-txn writes conflicting with txns

Closed

SERVER-40105 Improve diagnostic information in currentOp for excessive write conflicts and prepare conflicts

Closed

Assignee:: Benety Goh
Reporter:: Yujin Kang Park
Participants:: Benety Goh, Githook User, Max Hirschhorn, Yujin Kang Park
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jul 19 2023 04:04:13 PM UTC
Updated:: Oct 29 2023 09:18:43 PM UTC
Resolved:: Aug 29 2023 05:51:31 PM UTC
Confidence Status Last Update:: 21/Aug/23 7:24 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates