[DOCS-12965] Investigate changes in SERVER-41376: Track time transactions on mongos are active and inactive and include in slow txn logging Created: 19/Aug/19  Updated: 13/Nov/23  Resolved: 03/Dec/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-41376 Track time transactions on mongos are... Closed
Participants:
Days since reply: 4 years, 10 weeks, 1 day ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

This ticket updated the log message printed by mongos for slow transactions (or those run when the TXN log component verbosity is >= 1) to include the time transaction was active (processing a user request) vs. inactive (waiting for a user request).

Description of Linked Ticket

As per the scope document, track how long a transaction has been active (executing a client command) and inactive (waiting for a client command) and include both in the slow transaction log for all transactions.

This was spun off from SERVER-40985.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Kay Kim (Inactive) [ 03/Dec/19 ]

Currently, we don't document the content of log messages. We do state in https://docs.mongodb.com/manual/core/transactions/#diagnostics

the log messages includes information on slow transactions (i.e. transactions that exceed the :setting:`operationProfiling.slowOpThresholdMs` threshhold) under the :data:`TXN` log component.

If we need to be more specific later, can update the blurb to mention that the message includes both active and inactive timing info

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