-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
-
Execution Team 2021-11-01, Execution Team 2021-12-13, Execution Team 2021-12-27, Execution Team 2022-01-10, Execution Team 2022-02-07, Execution Team 2022-02-21, Execution Team 2022-03-07
When inserting a batch of documents and indexing them, we will loop through the ready indexes, and then for each index we will loop through the documents. If a later document with a higher timestamp causes an earlier index to become multikey, the write to _mdb_catalog will use the higher timestamp. If then an earlier document causes a later index to become multikey, the second write to the catalog will use the earlier timestamp, which is out of order.
- is related to
-
SERVER-60037 Enable the ordered timestamp assertion in MongoDB
- Closed
- related to
-
SERVER-65439 Tenant Migration oplog applier may try to wrongly mark an index as multikey.
- Closed