This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] 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 8f33b35c7b8 Docs sync done from apache/pulsar (#b61f3d5)
8f33b35c7b8 is described below
commit 8f33b35c7b897bbb9f0973732c326dff5650f228
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed Jul 1 01:49:22 2026 +0000
Docs sync done from apache/pulsar (#b61f3d5)
---
.../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 04ea06bfca1..18339d36b14 100644
--- a/static/reference/next/config/reference-configuration-broker.md
+++ b/static/reference/next/config/reference-configuration-broker.md
@@ -2424,6 +2424,17 @@ Grace period (seconds) the controller leader waits for a
disconnected scalable-t
**Category**: Policies
+### scalableTopicEntryBucketBudget
+Total entry-bucket budget per scalable topic. Entry-buckets are the unit of
key-shared consumption parallelism within a segment, so this budget is how many
consumers can share a single segment's keys. It is distributed across the
topic's segments (each gets floor(budget / segmentCount), at least 1): a
single-segment topic starts with the whole budget, and as the topic splits into
more segments each segment settles toward 1 bucket (full batching).
+
+**Type**: `int`
+
+**Default**: `4`
+
+**Dynamic**: `true`
+
+**Category**: Policies
+
### scalableTopicLoadReportIntervalSeconds
Interval (seconds) at which the segment-owning broker samples its segment
topics to report load for auto split/merge. Read at broker start; not dynamic.
diff --git a/static/reference/next/config/reference-configuration-standalone.md
b/static/reference/next/config/reference-configuration-standalone.md
index 04ea06bfca1..18339d36b14 100644
--- a/static/reference/next/config/reference-configuration-standalone.md
+++ b/static/reference/next/config/reference-configuration-standalone.md
@@ -2424,6 +2424,17 @@ Grace period (seconds) the controller leader waits for a
disconnected scalable-t
**Category**: Policies
+### scalableTopicEntryBucketBudget
+Total entry-bucket budget per scalable topic. Entry-buckets are the unit of
key-shared consumption parallelism within a segment, so this budget is how many
consumers can share a single segment's keys. It is distributed across the
topic's segments (each gets floor(budget / segmentCount), at least 1): a
single-segment topic starts with the whole budget, and as the topic splits into
more segments each segment settles toward 1 bucket (full batching).
+
+**Type**: `int`
+
+**Default**: `4`
+
+**Dynamic**: `true`
+
+**Category**: Policies
+
### scalableTopicLoadReportIntervalSeconds
Interval (seconds) at which the segment-owning broker samples its segment
topics to report load for auto split/merge. Read at broker start; not dynamic.
