-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution NAMER
-
Fully Compatible
-
ALL
-
v7.1, v7.0, v6.0
-
Execution NAMR Team 2023-08-21, Execution NAMR Team 2023-09-04
-
200
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The key phrase is: "checkReplicatedDataHashes, the two nodes have a different hash for the collection test.system.buckets.timeseries_internal_bounded_sort"
This is the destination cluster in a mongosync run. Notably, mongosync creates time-series collections by creating a system.buckets.mongosync.tmp.$srcUUID collection, then renaming it to the correct system.buckets name, then creating the view separately. That may be part of the cause.
- is related to
-
SERVER-81044 Handle internal oplog update correctly in transactions
-
- Closed
-
-
SERVER-101787 Add FCV gating for the checkExistenceForDiffInsert oplog field in v6.0
-
- Closed
-