[SERVER-41113] Ignore NamespaceNotFound exceptions when applying transactions during initial sync and recovery - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 4.1.14
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2019-06-03
Linked BF Score:
0

Description

The collection may have been dropped since we are applying operations out of order.

We ignore NamespaceNotFound errors in normal oplog application here.

But we don't do it here. The applyOps command doesn't seem to ignore these errors either, so wherever we use that code path to apply transaction operations we likely need to do the same.

This was found from code inspection and I haven't created a repro, so it's possible something prevents this from causing a problem.

It'll be interesting to see if the initial sync fuzzer catches this once it supports transactions, max.hirschhorn.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

initialSyncBug.js
1.52 MB
May 20 2019 09:13:25 PM UTC

Issue Links

is depended on by

SERVER-39993 Add kill and terminate versions of concurrency step down suites

Closed

is related to

SERVER-41163 During initial sync, failing to apply an update thats in a prepared txn hits an invariant

Closed

related to

SERVER-41284 Add failpoint to surface idempotency issues of transaction operations in initial sync

Closed

SERVER-39804 Extend the oplog idempotency test for new oplog entries

Closed

Activity

People

Assignee:: Matthew Russotto

Reporter:: Judah Schvimer

Participants:: Githook User, Judah Schvimer, Matthew Russotto, Samyukta Lanka, William Schultz

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: May 13 2019 04:12:02 PM UTC

Updated:: Jun 03 2019 02:17:23 PM UTC

Resolved:: May 30 2019 05:15:14 PM UTC