Track connections churned due to MaxTimeMs expiration on mongos

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In order to provide additional visibility into the impact that not having inline cancellation is having on the server (specifically in sharded clusters), lets add a metric that tracks how many connections are churned by the mongos to evaluate the impact of this cancellation model.

            Assignee:
            Unassigned
            Reporter:
            Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: