[SERVER-35148] Synchronously enable the profiler in prepare_conflict.js before starting a parallel transaction Created: 22/May/18  Updated: 29/Oct/23  Resolved: 22/May/18

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

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Storage NYC 2018-06-04
Participants:
Linked BF Score: 18

 Description   

The noPassthrough/prepare_confict.js test enables the profiler on a collection, which holds a MODE_X lock on the database, in parallel with beginning an update operation in a transaction. This occasionally results in a LockTimeout error on the update command.

Enabling the profiler with the profile command  should be moved so that it completes before doUpdateTransactionPrepare starts a parallel shell. This will ensure so that no conflicting locks prevent the update command from completing.



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

Author:

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

Message: SERVER-35148 Synchronously enable the profiler in prepare_conflict.js before starting a parallel transaction

(cherry picked from commit d4aa14a6e4abeb68e3d044d792b0011bfb8f3e98)
Branch: v4.0
https://github.com/mongodb/mongo/commit/44d9064c816f262fc1d972bde23dd755774fe4b8

Comment by Githook User [ 22/May/18 ]

Author:

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

Message: SERVER-35148 Synchronously enable the profiler in prepare_conflict.js before starting a parallel transaction
Branch: master
https://github.com/mongodb/mongo/commit/d4aa14a6e4abeb68e3d044d792b0011bfb8f3e98

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