[SERVER-44944] avoid taking the PBWM lock in SessionsCollectionRS::_isStandaloneOrPrimary() Created: 04/Dec/19  Updated: 29/Oct/23  Resolved: 13/Dec/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.3.3

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

Issue Links:
Depends
Related
is related to SERVER-38341 Remove Parallel Batch Writer Mutex Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-12-16
Participants:
Linked BF Score: 44

 Description   

SessionsCollectionRS::_isStandaloneOrPrimary() is used by the PeriodicJob for the LogicalSessionCache on both primaries and secondaries. Because this check relies implicitly on the PBWM lock, this process may be blocked on slow oplog application. It may be possible to modify this function to not require the PBWM lock.



 Comments   
Comment by Githook User [ 11/Dec/19 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-44944 SessionsCollectionRS::_isStandaloneOrPrimary() does not require the PBWM
Branch: master
https://github.com/mongodb/mongo/commit/ac9cb14962672d84fe0ab6935b87218c927ae6b4

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