[SERVER-83761] Consider renaming the ticket statistics in the execution layer Created: 30/Nov/23  Updated: 06/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Luke Pearson Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: storex-ranked
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-11-30-13-05-35-857.png    
Issue Links:
Related
Assigned Teams:
Storage Execution
Participants:

 Description   

Recently a number of support cases have highlighted the statistics

"ss wiredtiger concurrentTransactions read out"

"ss wiredtiger concurrentTransactions read totalTickets"

"ss wiredtiger concurrentTransactions write out"

"ss wiredtiger concurrentTransactions write totalTickets".

For example this FTDC image demonstrates a case where the write tickets are exhausted:

This statistic tends to cause confusion among both support and other engineers as it implicates the storage engine layer (it is even merged with WiredTiger stats by T2), however the storage engine doesn't maintain the ticketing system or have a concept of read/write tickets. This can lead to misdirected questions about ticket exhaustion and other issues with regards to ticketing.

As part of this work it may be worth sharing information with support as to what the ticketing system is, when it comes into affect and other related issues.



 Comments   
Comment by Steven Vannelli [ 12/Dec/23 ]

We're putting this toward the bottom of our prioritized backlog. When we do decide to pick it up, we will write an Engineering Proposal or scope to ensure stakeholders are aware of and onboard with the change.

Comment by James Lin [ 06/Dec/23 ]

From TS perspective, we agreed with shameek.ray@mongodb.com that "ticket" has been "a user-facing concept". For example, Atlas has even an alert "Tickets Available". today. I also agree with the motivation behind this JIRA as well as starting with a document (e.g. "Execution Control field guide").

Comment by Steven Vannelli [ 05/Dec/23 ]

Thanks shameek.ray@mongodb.com, getting a scope or eng proposal approved here seems reasonable if we decide to proceed with it. 

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