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