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 f38858cf436 Docs sync done from apache/pulsar (#94de2b6)
f38858cf436 is described below

commit f38858cf4363092fb1f3254b13b0d1482e1164fc
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed Jun 10 01:45:57 2026 +0000

    Docs sync done from apache/pulsar (#94de2b6)
---
 static/reference/next/config/reference-configuration-broker.md   | 9 ++++++---
 .../reference/next/config/reference-configuration-standalone.md  | 9 ++++++---
 static/reference/next/pulsar-perf/pulsar-perf.md                 | 1 +
 static/reference/next/pulsar/initialize-cluster-metadata.md      | 2 +-
 4 files changed, 14 insertions(+), 7 deletions(-)

diff --git a/static/reference/next/config/reference-configuration-broker.md 
b/static/reference/next/config/reference-configuration-broker.md
index 2144dfec527..2cc82520aaf 100644
--- a/static/reference/next/config/reference-configuration-broker.md
+++ b/static/reference/next/config/reference-configuration-broker.md
@@ -5706,11 +5706,14 @@ Maximum time to wait for acquiring permits for max 
reads in flight when managedL
 **Category**: Storage (Managed Ledger)
 
 ### managedLedgerMaxReadsInFlightSizeInMB
-Maximum buffer size for bytes read from storage. This is the memory retained 
by data read from storage (or cache) until it has been delivered to the 
Consumer Netty channel. Use O to disable
+Maximum buffer size in MB for bytes read from storage (or from the cache). 
This is the memory retained by data read from storage (or cache) until it has 
been delivered to the Consumer Netty channel. This provides backpressure for 
BookKeeper and tiered storage reads, preventing the broker from having too many 
concurrent reads and running into Out of Memory errors when there are multiple 
concurrent reads to multiple concurrent consumers.
+When left unset (empty), it defaults to the greater of 
dispatcherMaxReadSizeBytes and 15% of available JVM direct memory; 
dispatcherMaxReadSizeBytes is the minimum value so the limiter can never block 
the completion of a single read.
+Set to 0 to disable the feature.
+Set to a value greater than 0 to use that many MB.
 
-**Type**: `long`
+**Type**: `java.lang.Long`
 
-**Default**: `0`
+**Default**: `null`
 
 **Dynamic**: `false`
 
diff --git a/static/reference/next/config/reference-configuration-standalone.md 
b/static/reference/next/config/reference-configuration-standalone.md
index 2144dfec527..2cc82520aaf 100644
--- a/static/reference/next/config/reference-configuration-standalone.md
+++ b/static/reference/next/config/reference-configuration-standalone.md
@@ -5706,11 +5706,14 @@ Maximum time to wait for acquiring permits for max 
reads in flight when managedL
 **Category**: Storage (Managed Ledger)
 
 ### managedLedgerMaxReadsInFlightSizeInMB
-Maximum buffer size for bytes read from storage. This is the memory retained 
by data read from storage (or cache) until it has been delivered to the 
Consumer Netty channel. Use O to disable
+Maximum buffer size in MB for bytes read from storage (or from the cache). 
This is the memory retained by data read from storage (or cache) until it has 
been delivered to the Consumer Netty channel. This provides backpressure for 
BookKeeper and tiered storage reads, preventing the broker from having too many 
concurrent reads and running into Out of Memory errors when there are multiple 
concurrent reads to multiple concurrent consumers.
+When left unset (empty), it defaults to the greater of 
dispatcherMaxReadSizeBytes and 15% of available JVM direct memory; 
dispatcherMaxReadSizeBytes is the minimum value so the limiter can never block 
the completion of a single read.
+Set to 0 to disable the feature.
+Set to a value greater than 0 to use that many MB.
 
-**Type**: `long`
+**Type**: `java.lang.Long`
 
-**Default**: `0`
+**Default**: `null`
 
 **Dynamic**: `false`
 
diff --git a/static/reference/next/pulsar-perf/pulsar-perf.md 
b/static/reference/next/pulsar-perf/pulsar-perf.md
index d4ceed67c47..dd1a58dc148 100644
--- a/static/reference/next/pulsar-perf/pulsar-perf.md
+++ b/static/reference/next/pulsar-perf/pulsar-perf.md
@@ -102,6 +102,7 @@ $ pulsar-perf consume [options]
 | `-ns, --num-subscriptions` | Number of subscriptions (per topic)|1|
 | `-ss, --subscriptions` | A list of subscriptions to consume (for example, 
sub1,sub2)|[sub]|
 | `-st, --subscription-type` | Subscription type|Exclusive|
+| `-sct, --scalable-consumer-type` | V5 scalable-topic consumer API to use: 
Queue (unordered, individual ack) or Stream (ordered, cumulative ack, 1:1 
segment assignment). Use Stream with more consumers than segments to drive 
auto-split (PIP-483).|Queue|
 | `-sp, --subscription-position` | Subscription position|LATEST|
 | `-r, --rate` | Simulate a slow message consumer (rate in msg/s)|0.0|
 | `-q, --receiver-queue-size` | Size of the receiver queue|1000|
diff --git a/static/reference/next/pulsar/initialize-cluster-metadata.md 
b/static/reference/next/pulsar/initialize-cluster-metadata.md
index 66fd94b971c..30ea6f2db2c 100644
--- a/static/reference/next/pulsar/initialize-cluster-metadata.md
+++ b/static/reference/next/pulsar/initialize-cluster-metadata.md
@@ -1,4 +1,4 @@
-2026-06-09T01:41:56,768+0000 [main] INFO  
org.apache.bookkeeper.meta.MetadataDrivers - BookKeeper metadata driver manager 
initialized {}
+2026-06-10T01:45:31,898+0000 [main] INFO  
org.apache.bookkeeper.meta.MetadataDrivers - BookKeeper metadata driver manager 
initialized {}
 # initialize-cluster-metadata
 
 

Reply via email to