Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Sprint:
Storage Execution 2025-10-27, Storage Execution 2025-11-10
CAR Domain/s:
None

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

The multikey index field has known issues that can cause it to not match between nodes, specifically involving aborted transactions and logical initial sync. For this reason we should exclude including the hash of these fields in the overall metadata hash since it can cause a lot of noise during validating the fleet

is related to

SERVER-113189 Aborted multi-doc transaction can leave inconsistent multikey fields within a replica set

Backlog

SERVER-113190 Initial sync can create index entries with different multikey fields

Backlog

Assignee:: Yuhong Zhang
Reporter:: Sean Zimmerman
Participants:: Githook User, Sean Zimmerman, Yuhong Zhang
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Oct 10 2025 05:15:42 PM UTC
Updated:: Oct 30 2025 02:11:44 PM UTC
Resolved:: Oct 30 2025 02:11:44 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates