Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.1, 4.2.2
Affects Version/s: None
Component/s: Internal Code
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.2
Sprint:
Sharding 2019-02-11, Sharding 2019-10-21, Sharding 2019-11-04
Linked BF Score:
50
Confidence Status:
None
Work Order:
3

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

Right now if we want to wait for a failpoint to be hit from a jstest, we need to parse log output to wait until the failpoint outputs some log message. It'd be much easier if we had a waitForFailpoint command that could wait until a failpoint got hit. This would require some "barrier"-esque functionality on the failpoint, which could potentially be useful for its own reasons.

duplicates

SERVER-42308 Improve synchronization between two fail points

Backlog

is depended on by

SERVER-42471 Add the new waitForFailpoint mechanism to timestamped_reads_wait_for_prepare_oplog_visibility.js

Closed

is related to

SERVER-44251 Replace setFailPoint and clearFailPoint with configureFailPoint function in fail_point_util.js

Closed

related to

SERVER-48171 replace OperationContext with Interruptible in FailPoint API

Closed

Assignee:: Cheahuychou Mao
Reporter:: Matthew Saltz (Inactive)
Participants:: Cheahuychou Mao, Githook User, Lingzhi Deng, Matthew Saltz, Mira Carey, Siyuan Zhou
Votes:: 3 Vote for this issue
Watchers:: 11 Start watching this issue

Created:: Jan 23 2019 10:13:26 PM UTC
Updated:: Oct 29 2023 10:24:50 PM UTC
Resolved:: Oct 25 2019 07:11:53 PM UTC
Confidence Status Last Update:: 10/Oct/19 8:38 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates