Don't acquire ConnectionPool mutex upon stat collection

XMLWordPrintableJSON

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

      FTDC calls appendConnectionStats on the sharding task executor which will acquire the ConnectionPool's mutex. Under heavy load, this mutex could be contended and cause slowdowns in the FTDC thread. We should update the ConnectionPool to make `_pools` a VersionedValue and make all stats atomic. With these changes, we could collect ConnectionPool stats without acquiring it's mutex. 

            Assignee:
            Unassigned
            Reporter:
            Joseph Prince
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: