Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2026-04-27, CAR Team 2026-05-11, CAR Team 2026-05-25, CAR Team 2026-06-08, CAR Team 2026-06-22
Linked BF Score:
200
CAR Domain/s:
None

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

We perform writes to the catalog table on secondaries with different timestamps than the primary.

Example: secondary writes to catalog table at T1 despite the primary writing at T2:

Primary:

Some irrelevant write happens @ T1
Insert doc @ T2 with an indexed array
- Index is not multikey yet, so writes to catalog table, marking index as multikey. All happens in the same WT txn.

Secondary applying a batch of writes T1-T2: * Apply irrelevant op @ T1

Insert doc @ T2 with an indexed array
At end of batch, updates multikey info with the first timestamp in the batch, T1

depends on

SERVER-114087 Use consistent timestamp for multikey writes on the primary and secondary

Closed

is depended on by

SERVER-128070 Explore introducing a random sampling hook for timestamp consistency of multikeyness

In Code Review

is duplicated by

SERVER-114087 Use consistent timestamp for multikey writes on the primary and secondary

Closed

related to

SERVER-128354 Use transaction commit timestamp for deferred multikey entries with unknown timestamps

In Progress

Assignee:: Enrico Golfieri
Reporter:: Sandeep Dhoot (Inactive)
Participants:: Enrico Golfieri, Githook User, Sandeep Dhoot
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Sep 15 2025 05:28:03 PM UTC
Updated:: Jun 08 2026 01:26:35 PM UTC
Resolved:: Jun 08 2026 01:26:35 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates