From 162f853841b25797fe6c54c9a29269776ef66158 Mon Sep 17 00:00:00 2001 From: Jason Smith Date: Sat, 13 Mar 2021 11:35:30 -0600 Subject: [PATCH] Document max_request_bytes config --- website/docs/language/settings/backends/etcdv3.html.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website/docs/language/settings/backends/etcdv3.html.md b/website/docs/language/settings/backends/etcdv3.html.md index 7c31d5125..8f406b53d 100644 --- a/website/docs/language/settings/backends/etcdv3.html.md +++ b/website/docs/language/settings/backends/etcdv3.html.md @@ -54,3 +54,4 @@ The following configuration options / environment variables are supported: * `cacert_path` - (Optional) The path to a PEM-encoded CA bundle with which to verify certificates of TLS-enabled etcd servers. * `cert_path` - (Optional) The path to a PEM-encoded certificate to provide to etcd for secure client identification. * `key_path` - (Optional) The path to a PEM-encoded key to provide to etcd for secure client identification. + * `max_request_bytes` - (Optional) The max request size to send to etcd. This can be increased to enable storage of larger state. You must set the corresponding server-side flag [--max-request-bytes](https://etcd.io/docs/current/dev-guide/limit/#request-size-limit) as well and the value should be less than the client setting. Defaults to `2097152` (2.0 MiB). **Please Note:** Increasing etcd's request size limit may negatively impact overall latency.