Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.0.3, 6.1.0-rc4, 6.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v6.1, v6.0
Sprint:
Execution Team 2021-11-01, Execution Team 2021-11-15, Execution Team 2021-12-13, Execution Team 2021-12-27, Execution Team 2022-01-10, Execution Team 2022-01-24, Execution Team 2022-02-07, Execution Team 2022-02-21, Execution Team 2022-09-19
CAR Domain/s:
None

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

When recovering from oplogs as a standalone server, 'removeIndexBuildEntry()' can make untimestamped writes to 'config.system.indexBuilds' collection and '_mdb_catalog'.

depends on

SERVER-64760 Correctly timestamp catalog writes for index recovery when an oplog entry timestamp is present

Closed

is related to

SERVER-69589 Two-phase index builds can leave leftover entries in 'config.system.indexBuilds'

Blocked

SERVER-60037 Enable the ordered timestamp assertion in MongoDB

Closed

Assignee:: Gregory Wlodarek
Reporter:: Yuhong Zhang
Participants:: Githook User, Gregory Wlodarek, Yuhong Zhang
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Oct 15 2021 06:15:44 PM UTC
Updated:: Oct 29 2023 09:47:18 PM UTC
Resolved:: Sep 12 2022 04:09:42 PM UTC