This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 5380b963f34 Docs sync done from apache/pulsar (#1b74fe0)
5380b963f34 is described below
commit 5380b963f34a150c23e4588fdd6abb86c9960f40
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Sep 25 01:36:29 2025 +0000
Docs sync done from apache/pulsar (#1b74fe0)
---
.../next/config/reference-configuration-broker.md | 66 ++++++++++++++++++++++
.../config/reference-configuration-standalone.md | 66 ++++++++++++++++++++++
2 files changed, 132 insertions(+)
diff --git a/static/reference/next/config/reference-configuration-broker.md
b/static/reference/next/config/reference-configuration-broker.md
index 50818c5522d..48629169d17 100644
--- a/static/reference/next/config/reference-configuration-broker.md
+++ b/static/reference/next/config/reference-configuration-broker.md
@@ -2192,6 +2192,72 @@ Whether to enable precise time based backlog quota
check. Enabling precise time
**Category**: Policies
+### pulsarChannelPauseReceivingCooldownMs
+After the connection is recovered from an pause receiving state, the channel
will be rate-limited for a of time window to avoid overwhelming due to the
backlog of requests. This parameter defines how long the rate limiting should
last, in millis. Once the bytes that are waiting to be sent out reach the
"pulsarChannelWriteBufferHighWaterMark"， the timer will be reset. Setting a
negative value will disable the rate limiting.
+
+**Type**: `int`
+
+**Default**: `5000`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelPauseReceivingCooldownRateLimitPeriodMs
+After the connection is recovered from a pause receiving state, the channel
will be rate-limited for a period of time defined by
pulsarChannelPauseReceivingCooldownMs to avoid overwhelming due to the backlog
of requests. This parameter defines the period of the rate limiter in
milliseconds. If the rate limit period is set to 1000, then the unit is
requests per 1000 milli seconds. When it's 10, the unit is requests per every
10ms.
+
+**Type**: `int`
+
+**Default**: `10`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelPauseReceivingCooldownRateLimitPermits
+After the connection is recovered from a pause receiving state, the channel
will be rate-limited for a period of time to avoid overwhelming due to the
backlog of requests. This parameter defines how many requests should be allowed
in the rate limiting period.
+
+**Type**: `int`
+
+**Default**: `5`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelPauseReceivingRequestsIfUnwritable
+If enabled, the broker will pause reading from the channel to deal with new
request once the writer buffer is full, until it is changed to writable.
+
+**Type**: `boolean`
+
+**Default**: `false`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelWriteBufferHighWaterMark
+It relates to configuration "WriteBufferHighWaterMark" of Netty Channel
Config. If the number of bytes queued in the write buffer exceeds this value,
channel writable state will start to return "false".
+
+**Type**: `int`
+
+**Default**: `65536`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelWriteBufferLowWaterMark
+It relates to configuration "WriteBufferLowWaterMark" of Netty Channel Config.
If the number of bytes queued in the write buffer is smaller than this value,
channel writable state will start to return "true".
+
+**Type**: `int`
+
+**Default**: `32768`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
### resourceUsageTransportClassName
Default policy for publishing usage reports to system topic is disabled.This
enables publishing of usage reports
diff --git a/static/reference/next/config/reference-configuration-standalone.md
b/static/reference/next/config/reference-configuration-standalone.md
index 50818c5522d..48629169d17 100644
--- a/static/reference/next/config/reference-configuration-standalone.md
+++ b/static/reference/next/config/reference-configuration-standalone.md
@@ -2192,6 +2192,72 @@ Whether to enable precise time based backlog quota
check. Enabling precise time
**Category**: Policies
+### pulsarChannelPauseReceivingCooldownMs
+After the connection is recovered from an pause receiving state, the channel
will be rate-limited for a of time window to avoid overwhelming due to the
backlog of requests. This parameter defines how long the rate limiting should
last, in millis. Once the bytes that are waiting to be sent out reach the
"pulsarChannelWriteBufferHighWaterMark"， the timer will be reset. Setting a
negative value will disable the rate limiting.
+
+**Type**: `int`
+
+**Default**: `5000`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelPauseReceivingCooldownRateLimitPeriodMs
+After the connection is recovered from a pause receiving state, the channel
will be rate-limited for a period of time defined by
pulsarChannelPauseReceivingCooldownMs to avoid overwhelming due to the backlog
of requests. This parameter defines the period of the rate limiter in
milliseconds. If the rate limit period is set to 1000, then the unit is
requests per 1000 milli seconds. When it's 10, the unit is requests per every
10ms.
+
+**Type**: `int`
+
+**Default**: `10`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelPauseReceivingCooldownRateLimitPermits
+After the connection is recovered from a pause receiving state, the channel
will be rate-limited for a period of time to avoid overwhelming due to the
backlog of requests. This parameter defines how many requests should be allowed
in the rate limiting period.
+
+**Type**: `int`
+
+**Default**: `5`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelPauseReceivingRequestsIfUnwritable
+If enabled, the broker will pause reading from the channel to deal with new
request once the writer buffer is full, until it is changed to writable.
+
+**Type**: `boolean`
+
+**Default**: `false`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelWriteBufferHighWaterMark
+It relates to configuration "WriteBufferHighWaterMark" of Netty Channel
Config. If the number of bytes queued in the write buffer exceeds this value,
channel writable state will start to return "false".
+
+**Type**: `int`
+
+**Default**: `65536`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
+### pulsarChannelWriteBufferLowWaterMark
+It relates to configuration "WriteBufferLowWaterMark" of Netty Channel Config.
If the number of bytes queued in the write buffer is smaller than this value,
channel writable state will start to return "true".
+
+**Type**: `int`
+
+**Default**: `32768`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
### resourceUsageTransportClassName
Default policy for publishing usage reports to system topic is disabled.This
enables publishing of usage reports
