This is an automated email from the ASF dual-hosted git repository.
liuyu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 06c7758c4b2 [cleanup][doc] Deprecate ZK settings (#15127)
06c7758c4b2 is described below
commit 06c7758c4b2d3f87a1dfa605f97759cb9cc53090
Author: momo-jun <[email protected]>
AuthorDate: Tue Apr 19 15:06:25 2022 +0800
[cleanup][doc] Deprecate ZK settings (#15127)
---
site2/docs/reference-configuration.md | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/site2/docs/reference-configuration.md
b/site2/docs/reference-configuration.md
index af0f3656568..4b04273204e 100644
--- a/site2/docs/reference-configuration.md
+++ b/site2/docs/reference-configuration.md
@@ -305,6 +305,11 @@ brokerServiceCompactionThresholdInBytes|If the estimated
backlog size is greater
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
|managedLedgerCursorRolloverTimeInSeconds| Max time before triggering a
rollover on a cursor ledger |14400|
|managedLedgerMaxUnackedRangesToPersist| Max number of “acknowledgment holes”
that are going to be persistently stored. When acknowledging out of order, a
consumer will leave holes that are supposed to be quickly filled by acking all
the messages. The information of which messages are acknowledged is persisted
by compressing in “ranges” of messages that were acknowledged. After the max
number of ranges is reached, the information will only be tracked in memory and
messages will be redel [...]
+| managedLedgerMaxUnackedRangesToPersistInMetadataStore | Maximum number of
"acknowledgment holes" that can be stored in metadata store. If the number of
unacknowledged message range is higher than this limit, the broker persists
unacknowledged ranges into BookKeeper to avoid additional data overhead into
metadata store. | 1000 |
+| managedLedgerMetadataOperationsTimeoutSeconds | Operation timeout while
updating managed-ledger metadata. | 60 |
+| managedLedgerReadEntryTimeoutSeconds | Read entries timeout when the broker
tries to read messages from BookKeeper. | 0 |
+| managedLedgerAddEntryTimeoutSeconds | Add entry timeout when the broker
tries to publish messages to BookKeeper. | 0 |
+| managedLedgerNewEntriesCheckDelayInMillis | New entries check delay for the
cursor under the managed ledger. If no new messages in the topic, the cursor
tries to check again after the delay time. For consumption latency sensitive
scenarios, you can set the value to a smaller value or 0. A smaller value may
degrade consumption throughput.|10|
|autoSkipNonRecoverableData| Skip reading non-recoverable/unreadable
data-ledger under managed-ledger’s list.It helps when data-ledgers gets
corrupted at bookkeeper and managed-cursor is stuck at that ledger. |false|
|loadBalancerEnabled| Enable load balancer |true|
|loadBalancerPlacementStrategy| Strategy to assign a new bundle
weightedRandomSelection ||
@@ -395,7 +400,7 @@ The following parameters have been deprecated in the
`conf/broker.conf` file.
|configurationStoreServers| Configuration store connection string (as a
comma-separated list). Use `configurationMetadataStoreUrl` instead. |N/A|
|zooKeeperSessionTimeoutMillis| Zookeeper session timeout in milliseconds. Use
`metadataStoreSessionTimeoutMillis` instead. |30000|
|zooKeeperCacheExpirySeconds|ZooKeeper cache expiry time in seconds. Use
`metadataStoreCacheExpirySeconds` instead.|300|
-
+| managedLedgerMaxUnackedRangesToPersistInZooKeeper | Maximum number of
"acknowledgment holes" that can be stored in ZooKeeper. Use
`managedLedgerMaxUnackedRangesToPersistInMetadataStore` instead. | 1000 |
## Client
@@ -655,15 +660,14 @@ You can set the log level and configuration in the
[log4j2.yaml](https://github
|managedLedgerCursorRolloverTimeInSeconds| |14400|
| managedLedgerMaxSizePerLedgerMbytes | Maximum ledger size before triggering
a rollover for a topic. | 2048 |
| managedLedgerMaxUnackedRangesToPersist | Maximum number of "acknowledgment
holes" that are going to be persistently stored. When acknowledging out of
order, a consumer leaves holes that are supposed to be quickly filled by
acknowledging all the messages. The information of which messages are
acknowledged is persisted by compressing in "ranges" of messages that were
acknowledged. After the max number of ranges is reached, the information is
only tracked in memory and messages are redeli [...]
-| managedLedgerMaxUnackedRangesToPersistInZooKeeper | Maximum number of
"acknowledgment holes" that can be stored in Zookeeper. If the number of
unacknowledged message range is higher than this limit, the broker persists
unacknowledged ranges into bookkeeper to avoid additional data overhead into
Zookeeper. | 1000 |
+| managedLedgerMaxUnackedRangesToPersistInMetadataStore | Maximum number of
"acknowledgment holes" that can be stored in metadata store. If the number of
unacknowledged message range is higher than this limit, the broker persists
unacknowledged ranges into BookKeeper to avoid additional data overhead into
metadata store. | 1000 |
|autoSkipNonRecoverableData| |false|
| managedLedgerMetadataOperationsTimeoutSeconds | Operation timeout while
updating managed-ledger metadata. | 60 |
| managedLedgerReadEntryTimeoutSeconds | Read entries timeout when the broker
tries to read messages from BookKeeper. | 0 |
-| managedLedgerAddEntryTimeoutSeconds | Add entry timeout when the broker
tries to publish message to BookKeeper. | 0 |
-| managedLedgerNewEntriesCheckDelayInMillis | New entries check delay for the
cursor under the managed ledger. If no new messages in the topic, the cursor
tries to check again after the delay time. For consumption latency sensitive
scenario, you can set the value to a smaller value or 0. Of course, a smaller
value may degrade consumption throughput.|10 ms|
+| managedLedgerAddEntryTimeoutSeconds | Add entry timeout when the broker
tries to publish messages to BookKeeper. | 0 |
+| managedLedgerNewEntriesCheckDelayInMillis | New entries check delay for the
cursor under the managed ledger. If no new messages in the topic, the cursor
tries to check again after the delay time. For consumption latency sensitive
scenarios, you can set the value to a smaller value or 0. Of course, a smaller
value may degrade consumption throughput.|10|
| managedLedgerPrometheusStatsLatencyRolloverSeconds | Managed ledger
prometheus stats latency rollover seconds. | 60 |
| managedLedgerTraceTaskExecution | Whether to trace managed ledger task
execution time. | true |
-|managedLedgerNewEntriesCheckDelayInMillis|New entries check delay for the
cursor under the managed ledger. If no new messages in the topic, the cursor
will try to check again after the delay time. For consumption latency sensitive
scenario, it can be set to a smaller value or 0. A smaller value degrades
consumption throughput. By default, it is 10ms.|10|
|loadBalancerEnabled| |false|
|loadBalancerPlacementStrategy| |weightedRandomSelection|
|loadBalancerReportUpdateThresholdPercentage| |10|
@@ -721,6 +725,7 @@ The following parameters have been deprecated in the
`conf/standalone.conf` file
|zooKeeperOperationTimeoutSeconds|ZooKeeper operation timeout in seconds. Use
`metadataStoreOperationTimeoutSeconds` instead. |30|
|zooKeeperCacheExpirySeconds|ZooKeeper cache expiry time in seconds. Use
`metadataStoreCacheExpirySeconds` instead. |300|
|zooKeeperSessionTimeoutMillis| The ZooKeeper session timeout, in
milliseconds. Use `metadataStoreSessionTimeoutMillis` instead. |30000|
+| managedLedgerMaxUnackedRangesToPersistInZooKeeper | Maximum number of
"acknowledgment holes" that can be stored in ZooKeeper. Use
`managedLedgerMaxUnackedRangesToPersistInMetadataStore` instead. | 1000 |
## WebSocket
