Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Execution Team 2022-10-03
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

We use canAcceptWritesFor to determine if we're a primary which among other things, controls whether we should timestamp writing to the catalog. There are cases where we are writing to the catalog with a perfectly valid timestamp from an oplog entry, but we omit passing the timestamp to the transaction.

is depended on by

SERVER-60753 Removing index build entries from 'config.system.indexBuilds' can make mixed mode writes

Closed

split to

SERVER-69877 Remove untimestamped writes to the catalog when restarting unfinished index builds during startup recovery

Closed

Assignee:: Gregory Wlodarek
Reporter:: Daniel Gottlieb (Inactive)
Participants:: Daniel Gottlieb, Githook User, Gregory Wlodarek
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Mar 21 2022 07:15:42 PM UTC
Updated:: Oct 29 2023 09:40:47 PM UTC
Resolved:: Sep 23 2022 05:35:25 PM UTC
Confidence Status Last Update:: 19/Sep/22 8:28 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates