[SERVER-46639] OplogCapMaintainerThread should avoid flow control locks Created: 05/Mar/20  Updated: 29/Oct/23  Resolved: 09/Mar/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

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

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Execution Team 2020-03-09
Participants:

 Description   

A ticket is acquired with this lock acquisition.



 Comments   
Comment by Githook User [ 13/Mar/20 ]

Author:

{'username': 'DiannaHohensee', 'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-46639 Disable Flow Control for the internal OplogCapMaintainerThread

(cherry picked from commit 4fcabad68b0fb5d8fc16abcb334ca7991cb9c0e1)
Branch: v4.4
https://github.com/mongodb/mongo/commit/4d871ef8690346b0db4512c259b7830498155680

Comment by Githook User [ 09/Mar/20 ]

Author:

{'username': 'DiannaHohensee', 'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-46639 Disable Flow Control for the internal OplogCapMaintainerThread
Branch: master
https://github.com/mongodb/mongo/commit/4fcabad68b0fb5d8fc16abcb334ca7991cb9c0e1

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