[SERVER-34483] Avoid taking DBLocks when clearing in-memory database cache in FCV op observer if possible Created: 13/Apr/18  Updated: 29/Oct/23  Resolved: 26/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.4
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-34672 Unable to add shard on 3.7.5 sharded ... Closed
Problem/Incident
is caused by SERVER-34459 Clear in-memory database versions on ... Closed
Related
related to SERVER-37340 Make FCV upgrade use command oplog en... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-04-23, Sharding 2018-05-07
Participants:
Linked BF Score: 56

 Comments   
Comment by Githook User [ 26/Apr/18 ]

Author:

{'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi', 'name': 'Esha Maharishi'}

Message: SERVER-34483 Avoid taking DBLocks when clearing in-memory database cache in FCV op observer
Branch: master
https://github.com/mongodb/mongo/commit/751e985f0e1ecc30e2d49c3c2cb01c046dd5f8bb

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