[SERVER-48487] Use DBLock instead of AutoGetDB in onShardVersionMismatch Created: 29/May/20  Updated: 29/Oct/23  Resolved: 29/May/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

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

Issue Links:
Depends
Problem/Incident
is caused by SERVER-47975 Optimize ScopedShardVersionCriticalSe... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-06-01
Participants:
Linked BF Score: 30

 Description   

AutoGetDB can throw exceptions resulting in undefined behavior in ON_BLOCK_EXIT's destructor.



 Comments   
Comment by Githook User [ 29/May/20 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-48487 Use DBLock instead of AutoGetDB in onShardVersionMismatch
Branch: master
https://github.com/mongodb/mongo/commit/faefd048a4712423c31b8369927bb2f9be7f3f31

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