[SERVER-74236] Slow SessionWorkflow loop gets logged for streamable SDAM operations Created: 21/Feb/23  Updated: 27/Oct/23  Resolved: 21/Feb/23

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

Type: Bug Priority: Major - P3
Reporter: Divjot Arora (Inactive) Assignee: Amirsaman Memaripour
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-63883 Report operation latency from receivi... Backlog
Operating System: ALL
Participants:

 Description   

Per discussion with amirsaman.memaripour@mongodb.com, the "Slow SessionWorkflow loop" log message was recently added as part of the Cluster Connection Health Metrics project and logs operations that take longer than 5 seconds. However, streamable SDAM commands sent by drivers are supposed to hang for 10 seconds by default waiting for a topology change. Such commands should likely be excluded from this logging machinery.


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