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 57ef2b4d139b Docs sync done from apache/pulsar (#c2a0090)
57ef2b4d139b is described below
commit 57ef2b4d139bf4ae9ec754c940b826c7d5fa52dc
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Sat Sep 21 01:35:39 2024 +0000
Docs sync done from apache/pulsar (#c2a0090)
---
.../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 c6bebbf63b13..5590f3d7fa9f 100644
--- a/static/reference/next/config/reference-configuration-broker.md
+++ b/static/reference/next/config/reference-configuration-broker.md
@@ -1082,6 +1082,17 @@ After this delay, the service-unit state channel
tombstones any service units (e
**Category**: Load Balancer
+### loadBalancerServiceUnitTableViewSyncer
+Specify ServiceUnitTableViewSyncer to sync service unit(bundle) states between
metadata store and system topic table views during migration from one to the
other. One could enable this syncer before migration and disable it after the
migration finishes. It accepts `MetadataStoreToSystemTopicSyncer` or
`SystemTopicToMetadataStoreSyncer` to enable it. It accepts `None` to disable
it.
+
+**Type**:
`org.apache.pulsar.broker.ServiceConfiguration.ServiceUnitTableViewSyncerType`
+
+**Default**: `None`
+
+**Dynamic**: `true`
+
+**Category**: Load Balancer
+
### loadBalancerSheddingBundlesWithPoliciesEnabled
Option to automatically unload namespace bundles with affinity(isolation) or
anti-affinity group policies.Such bundles are not ideal targets to auto-unload
as destination brokers are limited.(only used in load balancer extension logics)
@@ -1172,6 +1183,17 @@ Name of load manager to use
**Category**: Load Balancer
+### loadManagerServiceUnitStateTableViewClassName
+Name of ServiceUnitStateTableView implementation class to use
+
+**Type**: `java.lang.String`
+
+**Default**:
`org.apache.pulsar.broker.loadbalance.extensions.channel.ServiceUnitStateTableViewImpl`
+
+**Dynamic**: `false`
+
+**Category**: Load Balancer
+
### lowerBoundarySheddingEnabled
When [current usage < average usage - threshold], the broker with the highest
load will be triggered to unload
diff --git a/static/reference/next/config/reference-configuration-standalone.md
b/static/reference/next/config/reference-configuration-standalone.md
index c6bebbf63b13..5590f3d7fa9f 100644
--- a/static/reference/next/config/reference-configuration-standalone.md
+++ b/static/reference/next/config/reference-configuration-standalone.md
@@ -1082,6 +1082,17 @@ After this delay, the service-unit state channel
tombstones any service units (e
**Category**: Load Balancer
+### loadBalancerServiceUnitTableViewSyncer
+Specify ServiceUnitTableViewSyncer to sync service unit(bundle) states between
metadata store and system topic table views during migration from one to the
other. One could enable this syncer before migration and disable it after the
migration finishes. It accepts `MetadataStoreToSystemTopicSyncer` or
`SystemTopicToMetadataStoreSyncer` to enable it. It accepts `None` to disable
it.
+
+**Type**:
`org.apache.pulsar.broker.ServiceConfiguration.ServiceUnitTableViewSyncerType`
+
+**Default**: `None`
+
+**Dynamic**: `true`
+
+**Category**: Load Balancer
+
### loadBalancerSheddingBundlesWithPoliciesEnabled
Option to automatically unload namespace bundles with affinity(isolation) or
anti-affinity group policies.Such bundles are not ideal targets to auto-unload
as destination brokers are limited.(only used in load balancer extension logics)
@@ -1172,6 +1183,17 @@ Name of load manager to use
**Category**: Load Balancer
+### loadManagerServiceUnitStateTableViewClassName
+Name of ServiceUnitStateTableView implementation class to use
+
+**Type**: `java.lang.String`
+
+**Default**:
`org.apache.pulsar.broker.loadbalance.extensions.channel.ServiceUnitStateTableViewImpl`
+
+**Dynamic**: `false`
+
+**Category**: Load Balancer
+
### lowerBoundarySheddingEnabled
When [current usage < average usage - threshold], the broker with the highest
load will be triggered to unload
