Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return 429 response on HTTP max connection limit #13621

Merged
merged 5 commits into from
Jul 20, 2022

Commits on Jul 6, 2022

  1. Return 429 response on HTTP max connection limit

    Instead of silently closing the connection, return a `429 Too Many Requests`
    HTTP response with a helpful error message to aid debugging when the
    connection limit is unintentionally reached.
    wjordan committed Jul 6, 2022
    Configuration menu
    Copy the full SHA
    39c2bbb View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    2b5f72b View commit details
    Browse the repository at this point in the history

Commits on Jul 15, 2022

  1. add rate-limit to connection-limiter error handler

    The rate-limit prevents the TLS handshake necessary to write the HTTP response
    from consuming too many server resources.
    Add "Too many concurrent connections" log warning when
    connection limit is reached.
    wjordan committed Jul 15, 2022
    Configuration menu
    Copy the full SHA
    3372c07 View commit details
    Browse the repository at this point in the history
  2. add nomad.agent.http.exceeded metric

    Count of HTTP connections exceeding concurrency limit.
    wjordan committed Jul 15, 2022
    Configuration menu
    Copy the full SHA
    9768e42 View commit details
    Browse the repository at this point in the history

Commits on Jul 20, 2022

  1. Configuration menu
    Copy the full SHA
    2b7de37 View commit details
    Browse the repository at this point in the history