mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-18 12:37:02 +02:00
0a06215d1a
* Document enabling config * Fix nav data JSON after disabling over-zealous prettifier * Address review feedback * Add warning about reloading config during overload * Bad metrics links * Another bad link * Add upgrade note about deprecation --------- Co-authored-by: Mike Palmiotto <mike.palmiotto@hashicorp.com>
33 lines
1007 B
Plaintext
33 lines
1007 B
Plaintext
---
|
|
layout: docs
|
|
page_title: Request Limiter - Configuration
|
|
description: |-
|
|
The Request Limiter mitigates overload scenarios in Vault by adaptively
|
|
limiting in-flight requests based on latency measurements.
|
|
---
|
|
|
|
# `request_limiter`
|
|
|
|
@include 'alerts/enterprise-only.mdx'
|
|
|
|
<Warning title="Deprecated beta feature">
|
|
|
|
Vault 1.16 included the request limiter as a Beta feature. During the beta, we
|
|
found an alternative approach that better meets user needs. The request limiter
|
|
has been deprecated in favor of [adaptive overload
|
|
protection](/vault/docs/concepts/adaptive-overload-protection).
|
|
|
|
</Warning>
|
|
|
|
The `request_limiter` stanza allows operators to turn on the adaptive
|
|
concurrency limiter, which is off by default. This is a reloadable config.
|
|
|
|
```hcl
|
|
request_limiter {
|
|
disable = false
|
|
}
|
|
```
|
|
|
|
~> **Warning** This feature is still in Tech Preview. Turning the Request
|
|
Limiter *on* may have negative effects on request success rates. Please test
|
|
your workloads before turning this on in production. |