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 46eba55c74ae Docs sync done from apache/pulsar (#38a41e0)
46eba55c74ae is described below

commit 46eba55c74ae7ec1c210a6df7f4ed7be6b6b81c8
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed Feb 26 01:36:35 2025 +0000

    Docs sync done from apache/pulsar (#38a41e0)
---
 .../reference/next/config/reference-configuration-broker.md   | 11 +++++++++++
 .../next/config/reference-configuration-standalone.md         | 11 +++++++++++
 2 files changed, 22 insertions(+)

diff --git a/static/reference/next/config/reference-configuration-broker.md 
b/static/reference/next/config/reference-configuration-broker.md
index ded59af48351..7f39cce7768c 100644
--- a/static/reference/next/config/reference-configuration-broker.md
+++ b/static/reference/next/config/reference-configuration-broker.md
@@ -3072,6 +3072,17 @@ If value is 
"org.apache.pulsar.broker.delayed.BucketDelayedDeliveryTrackerFactor
 
 **Category**: Server
 
+### dispatchRateLimiterFactoryClassName
+The class name of the factory that creates DispatchRateLimiter 
implementations. Current options are 
org.apache.pulsar.broker.service.persistent.DispatchRateLimiterFactoryAsyncTokenBucket
 (default, PIP-322 implementation) 
org.apache.pulsar.broker.service.persistent.DispatchRateLimiterFactoryClassic 
(legacy implementation)
+
+**Type**: `java.lang.String`
+
+**Default**: 
`org.apache.pulsar.broker.service.persistent.DispatchRateLimiterFactoryAsyncTokenBucket`
+
+**Dynamic**: `false`
+
+**Category**: Server
+
 ### dispatchThrottlingForFilteredEntriesEnabled
 Whether the broker should count filtered entries in dispatch rate limit 
calculations. When disabled, only messages sent to a consumer count towards a 
dispatch rate limit at the broker, topic, and subscription level. When enabled, 
messages filtered out due to entry filter logic are counted towards each 
relevant rate limit.
 
diff --git a/static/reference/next/config/reference-configuration-standalone.md 
b/static/reference/next/config/reference-configuration-standalone.md
index ded59af48351..7f39cce7768c 100644
--- a/static/reference/next/config/reference-configuration-standalone.md
+++ b/static/reference/next/config/reference-configuration-standalone.md
@@ -3072,6 +3072,17 @@ If value is 
"org.apache.pulsar.broker.delayed.BucketDelayedDeliveryTrackerFactor
 
 **Category**: Server
 
+### dispatchRateLimiterFactoryClassName
+The class name of the factory that creates DispatchRateLimiter 
implementations. Current options are 
org.apache.pulsar.broker.service.persistent.DispatchRateLimiterFactoryAsyncTokenBucket
 (default, PIP-322 implementation) 
org.apache.pulsar.broker.service.persistent.DispatchRateLimiterFactoryClassic 
(legacy implementation)
+
+**Type**: `java.lang.String`
+
+**Default**: 
`org.apache.pulsar.broker.service.persistent.DispatchRateLimiterFactoryAsyncTokenBucket`
+
+**Dynamic**: `false`
+
+**Category**: Server
+
 ### dispatchThrottlingForFilteredEntriesEnabled
 Whether the broker should count filtered entries in dispatch rate limit 
calculations. When disabled, only messages sent to a consumer count towards a 
dispatch rate limit at the broker, topic, and subscription level. When enabled, 
messages filtered out due to entry filter logic are counted towards each 
relevant rate limit.
 

Reply via email to