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 994e4b03fc0e Docs sync done from apache/pulsar (#81aed6c)
994e4b03fc0e is described below
commit 994e4b03fc0effe1d84d03d7150172baf7d413de
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Tue Jul 23 01:34:43 2024 +0000
Docs sync done from apache/pulsar (#81aed6c)
---
.../next/config/reference-configuration-broker.md | 22 ++++++++++++++++++++++
.../config/reference-configuration-standalone.md | 22 ++++++++++++++++++++++
2 files changed, 44 insertions(+)
diff --git a/static/reference/next/config/reference-configuration-broker.md
b/static/reference/next/config/reference-configuration-broker.md
index 01d9dffc641b..0630bdd90cab 100644
--- a/static/reference/next/config/reference-configuration-broker.md
+++ b/static/reference/next/config/reference-configuration-broker.md
@@ -1969,6 +1969,17 @@ Max pending publish requests per connection to avoid
keeping large number of pen
**Category**: Policies
+### maxSecondsToClearTopicNameCache
+A Specifies the minimum number of seconds that the topic name stays in memory,
to avoid clear cache frequently when there are too many topics are in use.
+
+**Type**: `int`
+
+**Default**: `7200`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
### maxTopicsPerNamespace
Max number of topics allowed to be created in the namespace. When the topics
reach the max topics of the namespace, the broker should reject the new topic
request(include topic auto-created by the producer or consumer) until the
number of connected consumers decrease. Using a value of 0, is disabling
maxTopicsPerNamespace-limit check.
@@ -2207,6 +2218,17 @@ Enable subscription types (default is all type enabled)
**Category**: Policies
+### topicNameCacheMaxCapacity
+Max capacity of the topic name cache. -1 means unlimited cache; 0 means broker
will clear all cache per maxSecondsToClearTopicNameCache, it does not mean
broker will not cache TopicName.
+
+**Type**: `int`
+
+**Default**: `100000`
+
+**Dynamic**: `true`
+
+**Category**: Policies
+
### topicPublisherThrottlingTickTimeMillis
Tick time to schedule task that checks topic publish rate limiting across all
topics Reducing to lower value can give more accuracy while throttling publish
but it uses more CPU to perform frequent check. (Disable publish throttling
with value 0)
diff --git a/static/reference/next/config/reference-configuration-standalone.md
b/static/reference/next/config/reference-configuration-standalone.md
index 01d9dffc641b..0630bdd90cab 100644
--- a/static/reference/next/config/reference-configuration-standalone.md
+++ b/static/reference/next/config/reference-configuration-standalone.md
@@ -1969,6 +1969,17 @@ Max pending publish requests per connection to avoid
keeping large number of pen
**Category**: Policies
+### maxSecondsToClearTopicNameCache
+A Specifies the minimum number of seconds that the topic name stays in memory,
to avoid clear cache frequently when there are too many topics are in use.
+
+**Type**: `int`
+
+**Default**: `7200`
+
+**Dynamic**: `false`
+
+**Category**: Policies
+
### maxTopicsPerNamespace
Max number of topics allowed to be created in the namespace. When the topics
reach the max topics of the namespace, the broker should reject the new topic
request(include topic auto-created by the producer or consumer) until the
number of connected consumers decrease. Using a value of 0, is disabling
maxTopicsPerNamespace-limit check.
@@ -2207,6 +2218,17 @@ Enable subscription types (default is all type enabled)
**Category**: Policies
+### topicNameCacheMaxCapacity
+Max capacity of the topic name cache. -1 means unlimited cache; 0 means broker
will clear all cache per maxSecondsToClearTopicNameCache, it does not mean
broker will not cache TopicName.
+
+**Type**: `int`
+
+**Default**: `100000`
+
+**Dynamic**: `true`
+
+**Category**: Policies
+
### topicPublisherThrottlingTickTimeMillis
Tick time to schedule task that checks topic publish rate limiting across all
topics Reducing to lower value can give more accuracy while throttling publish
but it uses more CPU to perform frequent check. (Disable publish throttling
with value 0)
