[SERVER-25612] Print oplog from primary and collect data files when secondary fails - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Backlog
Priority: Major - P3
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: Testing Infrastructure
Labels:

Assigned Teams:

Server Tooling & Methods
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Linked BF Score:
0

Description

When we have a failure during concurrent fuzzing while applying the oplog it would be helpful to have the data files to check what operation caused the fassert.

Attachments

Activity

People

Assignee:: Backlog - Server Tooling and Methods (STM) (Inactive)

Reporter:: DO NOT USE - Backlog - Test Infrastructure Group (TIG)

Participants:: Backlog - Server Tooling and Methods (STM), DO NOT USE - Backlog - Test Infrastructure Group (TIG), Steven Vannelli

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: Aug 15 2016 06:46:21 PM UTC

Updated:: Dec 06 2022 04:19:10 AM UTC