This is an automated email from the ASF dual-hosted git repository.
anmolnar pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/zookeeper.git
The following commit(s) were added to refs/heads/master by this push:
new f67ab635d ZOOKEEPER-5100: Fixed formatting of
configuration-parameters.mdx to fix website build
f67ab635d is described below
commit f67ab635d565440e7655826bc83fa64f828954cd
Author: Dávid Paksy <[email protected]>
AuthorDate: Fri Oct 2 21:41:24 2026 +0200
ZOOKEEPER-5100: Fixed formatting of configuration-parameters.mdx to fix
website build
Reviewers: anmolnar
Author: PDavid
Closes #2466 from PDavid/ZOOKEEPER-5100-website-lint-fix
---
.../configuration-parameters.mdx | 46 +++++++++++-----------
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git
a/zookeeper-website/app/pages/_docs/docs/_mdx/admin-ops/administrators-guide/configuration-parameters.mdx
b/zookeeper-website/app/pages/_docs/docs/_mdx/admin-ops/administrators-guide/configuration-parameters.mdx
index ef3a07e3d..333bcdbd3 100644
---
a/zookeeper-website/app/pages/_docs/docs/_mdx/admin-ops/administrators-guide/configuration-parameters.mdx
+++
b/zookeeper-website/app/pages/_docs/docs/_mdx/admin-ops/administrators-guide/configuration-parameters.mdx
@@ -624,29 +624,29 @@ property, when available, is noted below.
**New in 3.6.0:**
The size threshold after which a request is considered a large request. If
it is -1, then all requests are considered small, effectively turning off large
request throttling. The default is -1.
-* *multiRead.maxOps* :
- (Java system property: **zookeeper.multiRead.maxOps**)
- **New in 3.9.7:**
- The maximum number of read operations (getData / getChildren) permitted in
a single
- multiRead request. A multiRead can amplify a request that is small on the
wire into a
- very large in-memory response, because every sub-operation result is
materialized and
- held in memory before the response is serialized. This limit, together with
- *multiRead.maxResponseBytes*, bounds that amplification. A multiRead
exceeding this
- count is rejected with a BadArguments (Code = BADARGUMENTS) error and is
not executed.
- Note that neither *jute.maxbuffer* nor *largeRequestMaxBytes* protects
against this,
- as both bound only the inbound request, not the response it generates. Set
to 0 (or a
- negative value) to disable the check. The default is 1000.
-
-* *multiRead.maxResponseBytes* :
- (Java system property: **zookeeper.multiRead.maxResponseBytes**)
- **New in 3.9.7:**
- The maximum cumulative size, in bytes, of the data materialized while
serving a single
- multiRead request. This is the primary guard against a multiRead
response-amplification
- denial of service. The server accumulates the size of each sub-operation
result as the
- request is processed and rejects the request with a BadArguments (Code =
BADARGUMENTS)
- error as soon as the running total exceeds this value, before the full
response is built
- in heap. Set to 0 (or a negative value) to disable the check. The default
is 67108864
- (64 * 1024 * 1024, i.e. 64 MB).
+* _multiRead.maxOps_ :
+ (Java system property: **zookeeper.multiRead.maxOps**)
+ **New in 3.9.7:**
+ The maximum number of read operations (getData / getChildren) permitted in a
single
+ multiRead request. A multiRead can amplify a request that is small on the
wire into a
+ very large in-memory response, because every sub-operation result is
materialized and
+ held in memory before the response is serialized. This limit, together with
+ _multiRead.maxResponseBytes_, bounds that amplification. A multiRead
exceeding this
+ count is rejected with a BadArguments (Code = BADARGUMENTS) error and is not
executed.
+ Note that neither _jute.maxbuffer_ nor _largeRequestMaxBytes_ protects
against this,
+ as both bound only the inbound request, not the response it generates. Set
to 0 (or a
+ negative value) to disable the check. The default is 1000.
+
+* _multiRead.maxResponseBytes_ :
+ (Java system property: **zookeeper.multiRead.maxResponseBytes**)
+ **New in 3.9.7:**
+ The maximum cumulative size, in bytes, of the data materialized while
serving a single
+ multiRead request. This is the primary guard against a multiRead
response-amplification
+ denial of service. The server accumulates the size of each sub-operation
result as the
+ request is processed and rejects the request with a BadArguments (Code =
BADARGUMENTS)
+ error as soon as the running total exceeds this value, before the full
response is built
+ in heap. Set to 0 (or a negative value) to disable the check. The default is
67108864
+ (64 \* 1024 \* 1024, i.e. 64 MB).
- _outstandingHandshake.limit_
(Java system property only:
**zookeeper.netty.server.outstandingHandshake.limit**)
