[SERVER-34142] Background index builds for RTT on startup replication recovery corrupt _mdb_catalog - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: 3.7.4
Fix Version/s: 3.7.4
Component/s: Replication
Labels:
- rollback-functional

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2018-04-09
Linked BF Score:
21

Description

The LogicalClock is not initialized when performing replication recovery at startup. Completing a background secondary[1] index must set a legal timestamp. However the predicate to assign a timestamp fails because `startup` is not guaranteed to have a valid logical clock state.

[1] It's perhaps unclear why I call the index build a background secondary index build. The index build is kicked off by an oplog entry and as such intersects much of the same code path as a typical secondary index build.

Attachments

Issue Links

is duplicated by

SERVER-30939 Multiple index builds on same collection can livelock on WriteConflictExceptions

Closed

is related to

SERVER-43097 Improve log messaging when index builds get foregrounded because of startup recovery

Closed

related to

SERVER-30939 Multiple index builds on same collection can livelock on WriteConflictExceptions

Closed

Activity

People

Assignee:: Daniel Gottlieb (Inactive)

Reporter:: Daniel Gottlieb (Inactive)

Participants:: Daniel Gottlieb, Githook User, Kyle Suarez

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: Mar 27 2018 01:48:08 AM UTC

Updated:: Sep 05 2019 01:34:06 PM UTC

Resolved:: Apr 06 2018 07:24:03 PM UTC