-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
None
-
Fully Compatible
-
ALL
-
v4.0
-
Storage NYC 2018-06-04
-
63
If a user creates more than one index at a time, then all index completion (the ready: true write) is done at the timestamp of the last oplog entry.
This is because the transaction calls are sequenced as such:
- Index A is ready
- Index B is ready
- Set timestamp to T1
- Write oplog entry for index A
- Set timestamp to T2
- Write oplog entry for index B
- is related to
-
SERVER-34777 multi-index drops are given the wrong timestamps
- Closed
- related to
-
SERVER-38745 MigrationDestinationManager assigns incorrect timestamps while building multiple indexes
- Closed