Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-74236

Slow SessionWorkflow loop gets logged for streamable SDAM operations

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • None
    • None
    • None
    • None
    • ALL

    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.

      Attachments

        Issue Links

          Activity

            People

              amirsaman.memaripour@mongodb.com Amirsaman Memaripour
              divjot.arora@mongodb.com Divjot Arora (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: