[SERVER-30639] Timestamp bulk writes Created: 14/Aug/17  Updated: 30/Oct/23  Resolved: 14/Sep/17

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Eric Milkie
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-30827 Provide new interface for getting new... Closed
Related
related to SERVER-31514 ReplicationCoordinatorExternalStateIm... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2017-08-21, Storage 2017-09-11, Storage 2017-10-02
Participants:

 Description   

Bulk insert writes multiple data items and multiple oplog entries in one transaction. The code needs to be changed so that these writes are timestamped correctly. This will involve changing the order of writes so that oplog entries are written prior to the data – this way, the code will have already prepped the transaction with the proper timestamp when data writes happen.



 Comments   
Comment by Ramon Fernandez Marina [ 13/Sep/17 ]

Author:

{'username': u'milkie', 'name': u'Eric Milkie', 'email': u'milkie@10gen.com'}

Message:SERVER-30639 change getNextOpTimes interface to return a value
Branch:master
https://github.com/mongodb/mongo/commit/dc22fc57bff9e804ef42fbbf19e8f685a2cb434e

Comment by Ramon Fernandez Marina [ 12/Sep/17 ]

Author:

{'username': u'milkie', 'name': u'Eric Milkie', 'email': u'milkie@10gen.com'}

Message:SERVER-30827 SERVER-30639 Timestamp bulk writes via changes to optime generator
Branch:master
https://github.com/mongodb/mongo/commit/6264d36ac6002b296aa41b8dc79400fcc2cbdd74

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