Run rate limiter passthroughs with auth enabled to allow handshaking connections to not be rate limited

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • Workload Resilience 2026-02-02, Workload Resilience 2026-02-16, Workload Resilience 2026-03-02, Workload Resilience 2026-03-16, Workload Resilience 2026-03-30, Workload Resilience 2026-04-13, Workload Resilience 2026-05-11, Workload Resilience 2026-04-13, Workload Resilience 2026-05-25, ClusterScalability 25May-5June, ClusterScalability 8Jun-22June
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently rate limiter passthroughs do not run with auth enabled. This causes the rate limiter failpoint to potentially trigger on connection handshake with no way to opt out. Current opt-out strategies use the client's appName, which isn't yet parsed until after the first time a client establishes a connection on a node.

            Assignee:
            Jack Mulrow
            Reporter:
            Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: