[SERVER-34777] multi-index drops are given the wrong timestamps Created: 01/May/18  Updated: 29/Oct/23  Resolved: 18/May/18

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

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-34580 Plumb operation time to `getMinimumVi... Closed
related to SERVER-35070 multi index creates are given wrong t... Closed
related to SERVER-48772 Dropping multiple indexes incorrectly... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-05-21
Participants:
Linked BF Score: 0

 Description   

If a user drops more than one index at a time, then all drops will be given the timestamp of the last index drop, since the drops occur and then we write all of the oplog entries.



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

Author:

{'username': 'louiswilliams', 'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com'}

Message: SERVER-34777 Multi-index drops should timestamp each drop individually along with its oplog entry.
Branch: master
https://github.com/mongodb/mongo/commit/9ca43580864a05c6eb543b5bee8402d82bd99bc7

Comment by Judah Schvimer [ 10/May/18 ]

This is part of the work required to make this invariant into an equality invariant rather than a less than or equal to invariant.

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