[SERVER-35070] multi index creates are given wrong timestamps Created: 18/May/18  Updated: 29/Oct/23  Resolved: 30/May/18

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 4.0.0-rc1, 4.1.1

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-38745 MigrationDestinationManager assigns i... Closed
is related to SERVER-34777 multi-index drops are given the wrong... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Storage NYC 2018-06-04
Participants:
Linked BF Score: 63

 Description   

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:

  1. Index A is ready
  2. Index B is ready
  3. Set timestamp to T1
  4. Write oplog entry for index A
  5. Set timestamp to T2
  6. Write oplog entry for index B


 Comments   
Comment by Githook User [ 30/May/18 ]

Author:

{'username': 'dgottlieb', 'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com'}

Message: SERVER-35070: Timestamp index completions individually.

(cherry picked from commit 39694ed5ee47848c3e51f8b739e9ccad8ca54c69)
Branch: v4.0
https://github.com/mongodb/mongo/commit/4616b071591bbe2fac69d57177d7b1c4c2ce8598

Comment by Githook User [ 30/May/18 ]

Author:

{'username': 'dgottlieb', 'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com'}

Message: SERVER-35070: Timestamp index completions individually.
Branch: master
https://github.com/mongodb/mongo/commit/39694ed5ee47848c3e51f8b739e9ccad8ca54c69

Generated at Thu Feb 08 04:38:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.