[SERVER-44821] retrieving storage stats for currentOp blocked by slow oplog application Created: 25/Nov/19  Updated: 29/Oct/23  Resolved: 08/Jan/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.14

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:
Backports
Depends
Related
related to SERVER-44822 update indexing tests to avoid loggin... Closed
related to SERVER-44859 plan_cache_index_create.js is blocked... Closed
related to SERVER-45007 PBWM acquisition in GlobalLock constr... Closed
related to SERVER-39218 Simultaneous index builds improvement... Closed
related to SERVER-76851 remove unnecessary latch predicate in... Closed
is related to SERVER-38341 Remove Parallel Batch Writer Mutex Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2020-01-13
Participants:
Linked BF Score: 20

 Description   

On a secondary node, the currentOp command includes storage stats in its slow op log. If oplog application is taking too long to apply a batch of operations, this may prevent the currentOp from completing in a timely manner.

=========

The defect addressed here primarily involves the Parallel Batch Writer Mutex (PBWM), a logical resource that is required for oplog application on a secondary node. Prior to this fix, it was possible for the database profiler and the currentOp command to compete for the PBWM resource with secondary oplog application.



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

Author:

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

Message: SERVER-44821 accessing db.system.profile and currentOp storage stats should not conflict with slow oplog application

(cherry picked from commit 87bcfd4931e002bcfdb563d58bde06e32aca1d8d)
Branch: v4.2
https://github.com/mongodb/mongo/commit/46d92ea10a90b8d1330f9e42e90783419598abd8

Comment by Githook User [ 08/Jan/20 ]

Author:

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

Message: SERVER-44821 logging slow ops should not conflict with two phase index commits
Branch: master
https://github.com/mongodb/mongo/commit/d401d80a2c89d89db26750956cb3b3261e595a34

Comment by Githook User [ 08/Jan/20 ]

Author:

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

Message: SERVER-44821 accessing db.system.profile and currentOp storage stats should not conflict with slow oplog application
Branch: master
https://github.com/mongodb/mongo/commit/87bcfd4931e002bcfdb563d58bde06e32aca1d8d

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