[SERVER-33792] PBWM accounting should be separate from "Global" lock Created: 09/Mar/18  Updated: 06/Dec/22  Resolved: 05/Oct/18

Status: Closed
Project: Core Server
Component/s: Diagnostics, MMAPv1, Replication, Storage
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: SWDI
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Currently, resourceIdParallelBatchWriterMode is a ResourceId of type RESOURCE_GLOBAL. This is problematic, as the lock stats collector overlaps this resource id with the main Global one and they show up together as simply one "Global" entry in currentOp and Top output.
Normally this isn't too much of a problem, since the PBWM and the Global lock are acquired and released in lock step. However, it does make things very confusing when trying to diagnose certain types of problems, since WiredTiger read/write tickets are acquired in between the acquisition of PBWM and Global.

We should change the ResourceId type so that the PBWM shows up (and accrues stats) separately from the main Global lock.



 Comments   
Comment by Sara Williamson [ 05/Oct/18 ]

The changes necessary for this are too destabilizing for the stable branches. milkie

Comment by Eric Milkie [ 04/Apr/18 ]

While this work may be obviated by SERVER-20328 in the master branch, it still has value for the 3.4 and 3.6 branches, and may not actually be that much work to achieve.

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