[SERVER-55658] Out-of-order destruction of AutoGet* objects can lead to transaction closure Created: 31/Mar/21  Updated: 29/Oct/23  Resolved: 16/Apr/21

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

Type: Bug Priority: Major - P3
Reporter: Nikita Lapkov (Inactive) Assignee: Mihai Andrei
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-54515 [SBE] jstests/core/sort_merge.js fail... Closed
is depended on by SERVER-53942 Make all test cases in jstests/noPass... Closed
Related
related to SERVER-54066 Out-of-order destruction of multiple ... Closed
related to SERVER-57722 Test-only "sbe" command must hold an ... Closed
is related to SERVER-56087 Enable "jsCore_minimum_batch_size" pa... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query Execution 2021-04-19
Participants:
Linked BF Score: 166

 Description   

Steps to reproduce:

  1. AutoGetCollectionForReadMaybeLockFree number one is created
  2. AutoGetCollectionForReadMaybeLockFree number two is created
  3. We destroy the first object
  4. Deep underneath this object holds GlobalLock, which thinks it is outermost, since it was created first
  5. GlobalLock calls abandonSnapshot(), closing transaction and reseting the cursors


 Comments   
Comment by Githook User [ 16/Apr/21 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}

Message: SERVER-55658 Out-of-order destruction of AutoGet* objects can lead to transaction closure
Branch: master
https://github.com/mongodb/mongo/commit/4439ec4f5d4c91a049f050e886238342476ba1ab

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