Consider adding RST/connection_reset to condition of connection pool single drop

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Workload Resilience
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Follow up of SERVER-123418, see details of this comment.

      In the test of Linux we only observed FIN as asio code for connection rate limiter rejection, review if we should include "connection_reset" as well (it was added for Windows)

      Run `shard_connection_storm_rate_limited_locust` in default TLS enabled and TLS disabled, neither should show major regressions against baseline.

            Assignee:
            Unassigned
            Reporter:
            Haiyin Gu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: