-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
ALL
-
v4.4, v4.2, v4.0, v3.6
-
Execution Team 2020-10-19
-
10
When we rename a collection across databases, we internally copy it. The copy operation writes multiple documents within a write unit of work without reserving timestamps, which results in wrong timestamps. We need to make sure the timestamps are written correctly.
It is possible that this could just be a matter of using write_ops_exec insertDocuments rather than writing the documents in a loop and directly calling Collection::insertDocument.
- duplicates
-
SERVER-48771 Enforce constraints on "multi-timestamp" transactions
- Closed