[SERVER-31882] For vectored inserts, start transaction prior to assigning first timestamp Created: 08/Nov/17  Updated: 30/Oct/23  Resolved: 09/Nov/17

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

Type: Task 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
is depended on by SERVER-31694 17% throughput regression in insert w... Closed
Related
related to SERVER-31933 Add prepareSnapshot method to avoid d... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-11-13
Participants:
Linked BF Score: 0

 Description   

Assigning the first timestamp implicitly starts the transaction, under a hot mutex.



 Comments   
Comment by Githook User [ 14/Nov/17 ]

Author:

{'name': 'Geert Bosch', 'username': 'GeertBosch', 'email': 'geert@mongodb.com'}

Message: Revert "SERVER-31882 start a transaction when beginning a UnitOfWork"

This reverts commit 9a7ab2468ec94462890395cc591cd629d1dd9f7c.
Branch: master
https://github.com/mongodb/mongo/commit/351b4b12e45c7307d1bde5075d91b189423342c6

Comment by Githook User [ 09/Nov/17 ]

Author:

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

Message: SERVER-31882 start a transaction when beginning a UnitOfWork

In order to avoid implicitly starting a transaction under a hot mutex for vectored inserts,
this commit explicitly starts a transaction when beginUnitOfWork is called.
Branch: master
https://github.com/mongodb/mongo/commit/9a7ab2468ec94462890395cc591cd629d1dd9f7c

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