(pulsar-site) branch main updated: Docs sync done from apache/pulsar (#90f174d)

[gi...@apache.org]

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 de17f3c9270 Docs sync done from apache/pulsar (#90f174d)
de17f3c9270 is described below

commit de17f3c92702d6484ccd53507e57cea3406a1291
Author: github-actions[bot] <41...@users.noreply.github.com>
AuthorDate: Fri Oct 16 01:19:31 2026 +0000

    Docs sync done from apache/pulsar (#90f174d)
---
 static/reference/next/config/reference-configuration-broker.md     | 4 ++--
 static/reference/next/config/reference-configuration-standalone.md | 4 ++--
 static/reference/next/pulsar-admin/ns-isolation-policy.md          | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/static/reference/next/config/reference-configuration-broker.md b/static/reference/next/config/reference-configuration-broker.md
index f0879a47552..ce272293e54 100644
--- a/static/reference/next/config/reference-configuration-broker.md
+++ b/static/reference/next/config/reference-configuration-broker.md
@@ -5622,7 +5622,7 @@ If value is NONE, then save the ManagedCursorInfo bytes data directly.
 **Category**: Storage (Managed Ledger)
 
 ### managedLedgerAddEntryHandoverMaxBatchBytesSize
-Total size in bytes of the entries after which a batch of add entry requests handed over to the managed ledger's executor thread stops taking more. This keeps a ledger with large entries from occupying the executor thread for as long as a full batch of managedLedgerAddEntryHandoverMaxBatchItems adds would, which would delay add completions, reads and cursor notifications for the ledgers that share the thread. A batch always takes at least one add, even one whose entry is larger than this [...]
+Maximum total entry size in bytes of a batch of add entry requests handed over to the managed ledger's executor thread. This keeps a ledger with large entries from occupying the executor thread for as long as a full batch of managedLedgerAddEntryHandoverMaxBatchItems adds would, which would delay add completions, reads and cursor notifications for the ledgers that share the thread. An entry larger than this runs in a batch of its own. Set to 0 to limit batches only by their number of add [...]
 
 **Type**: `long`
 
@@ -5633,7 +5633,7 @@ Total size in bytes of the entries after which a batch of add entry requests han
 **Category**: Storage (Managed Ledger)
 
 ### managedLedgerAddEntryHandoverMaxBatchItems
-Maximum number of add entry requests handed over to the managed ledger's executor thread in one batch. Publishing threads queue adds for the ledger's executor, which takes them over in batches of up to this many adds and processes each batch before other tasks on that thread can run. A batch also stops taking adds once their entries add up to managedLedgerAddEntryHandoverMaxBatchBytesSize bytes. A larger value reduces scheduling overhead and contention between publishing threads under hi [...]
+Maximum number of add entry requests handed over to the managed ledger's executor thread in one batch. Publishing threads queue adds for the ledger's executor, which takes them over in batches of up to this many adds and processes each batch before other tasks on that thread can run. A batch also stops before taking an entry that would exceed managedLedgerAddEntryHandoverMaxBatchBytesSize bytes. A larger value reduces scheduling overhead and contention between publishing threads under hi [...]
 
 **Type**: `int`
 
diff --git a/static/reference/next/config/reference-configuration-standalone.md b/static/reference/next/config/reference-configuration-standalone.md
index f0879a47552..ce272293e54 100644
--- a/static/reference/next/config/reference-configuration-standalone.md
+++ b/static/reference/next/config/reference-configuration-standalone.md
@@ -5622,7 +5622,7 @@ If value is NONE, then save the ManagedCursorInfo bytes data directly.
 **Category**: Storage (Managed Ledger)
 
 ### managedLedgerAddEntryHandoverMaxBatchBytesSize
-Total size in bytes of the entries after which a batch of add entry requests handed over to the managed ledger's executor thread stops taking more. This keeps a ledger with large entries from occupying the executor thread for as long as a full batch of managedLedgerAddEntryHandoverMaxBatchItems adds would, which would delay add completions, reads and cursor notifications for the ledgers that share the thread. A batch always takes at least one add, even one whose entry is larger than this [...]
+Maximum total entry size in bytes of a batch of add entry requests handed over to the managed ledger's executor thread. This keeps a ledger with large entries from occupying the executor thread for as long as a full batch of managedLedgerAddEntryHandoverMaxBatchItems adds would, which would delay add completions, reads and cursor notifications for the ledgers that share the thread. An entry larger than this runs in a batch of its own. Set to 0 to limit batches only by their number of add [...]
 
 **Type**: `long`
 
@@ -5633,7 +5633,7 @@ Total size in bytes of the entries after which a batch of add entry requests han
 **Category**: Storage (Managed Ledger)
 
 ### managedLedgerAddEntryHandoverMaxBatchItems
-Maximum number of add entry requests handed over to the managed ledger's executor thread in one batch. Publishing threads queue adds for the ledger's executor, which takes them over in batches of up to this many adds and processes each batch before other tasks on that thread can run. A batch also stops taking adds once their entries add up to managedLedgerAddEntryHandoverMaxBatchBytesSize bytes. A larger value reduces scheduling overhead and contention between publishing threads under hi [...]
+Maximum number of add entry requests handed over to the managed ledger's executor thread in one batch. Publishing threads queue adds for the ledger's executor, which takes them over in batches of up to this many adds and processes each batch before other tasks on that thread can run. A batch also stops before taking an entry that would exceed managedLedgerAddEntryHandoverMaxBatchBytesSize bytes. A larger value reduces scheduling overhead and contention between publishing threads under hi [...]
 
 **Type**: `int`
 
diff --git a/static/reference/next/pulsar-admin/ns-isolation-policy.md b/static/reference/next/pulsar-admin/ns-isolation-policy.md
index 418490134d0..71e2c96ded7 100644
--- a/static/reference/next/pulsar-admin/ns-isolation-policy.md
+++ b/static/reference/next/pulsar-admin/ns-isolation-policy.md
@@ -24,8 +24,8 @@ $ pulsar-admin ns-isolation-policy set options
 |Flag|Description|Default|
 |---|---|---|
 | `[--namespaces]` | comma separated namespaces-regex list|null|
-| `[--primary]` | comma separated  primary-broker-regex list. In Pulsar, when namespaces (more specifically, namespace bundles) are assigned dynamically to brokers, the namespace isolation policy limits the set of brokers that can be used for assignment. Before topics are assigned to brokers, you can set the namespace isolation policy with a primary or a secondary regex to select desired brokers. If no broker matches the specified regex, you cannot create a topic. If there are not enough [...]
-| `[--secondary]` | comma separated secondary-broker-regex list|[]|
+| `[--primary]` | comma separated  primary-broker-regex list. In Pulsar, when namespaces (more specifically, namespace bundles) are assigned dynamically to brokers, the namespace isolation policy limits the set of brokers that can be used for assignment. Before topics are assigned to brokers, you can set the namespace isolation policy with a primary or a secondary regex to select desired brokers. If no broker matches the specified regex, you cannot create a topic. If there are not enough [...]
+| `[--secondary]` | comma separated secondary-broker-regex list. Regexes are matched in the same way as for --primary.|[]|
 | `[--auto-failover-policy-type]` | auto failover policy type name ['min_available']|null|
 | `[--auto-failover-policy-params]` | comma separated name=value auto failover policy parameters|null|
 | `[--unload-scope]` | configure the type of unload to do - ['all_matching', 'none', 'changed'] namespaces. By default, only namespaces whose placement will actually change would be unloaded and placed again. You can choose to not unload any namespace while setting this new policy by choosing `none` or choose to unload all namespaces matching old (if any) and new namespace regex. If you chose 'none', you will need to manually unload the namespaces for them to be placed correctly, or wait [...]