Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.7, 5.0.0-rc0
Affects Version/s: None
Component/s: Testing Infrastructure
Labels:
- newgrad

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.0, v4.4
Sprint:
Execution Team 2021-02-22, Execution Team 2021-03-08
Confidence Status:
None
Work Order:
3

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

In an attempt to reproduce some failures, I noticed we have remarkably little coverage of handling spurious WriteConflicts, especially in operations where they are normally unexpected. While most of our code is designed to handle such cases, I think we should exercise these code paths more often, since WiredTiger can return WT_ROLLBACK at any time.

I would suggest enabling the WTWriteConflictException and WTWriteConflictExceptionForReads fail points to a very low frequency (e.g. < 1%) so that most operations can make some progress.

depends on

SERVER-51526 Hybrid index builds can miss writes and crash in the event of a well-timed WriteConflictException

Closed

SERVER-51593 Index build bulk builder does not handle WriteConflictExceptions

Closed

SERVER-51656 CollectionBulkLoader does not handle write conflicts

Closed

is related to

SERVER-21332 Add FSM runners that always enable the WTWriteConflictException failpoint

Closed

Assignee:: Bynn Lee
Reporter:: Louis Williams
Participants:: Bynn Lee, Githook User, Louis Williams, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Apr 25 2019 03:55:28 PM UTC
Updated:: Oct 29 2023 10:21:41 PM UTC
Resolved:: Feb 26 2021 08:30:20 PM UTC
Confidence Status Last Update:: 16/Feb/21 6:05 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates