Slow SessionWorkflow loop gets logged for streamable SDAM operations

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Amirsaman Memaripour
              Reporter:
              Divjot Arora (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: