This is an automated email from the ASF dual-hosted git repository.
hjf 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 8ceaf43 fix format issue (#9158)
8ceaf43 is described below
commit 8ceaf4313cd8120e367dad4befc8b8fc66cc5ff0
Author: Jennifer Huang <[email protected]>
AuthorDate: Wed Jan 13 11:44:12 2021 +0800
fix format issue (#9158)
---
site2/docs/reference-configuration.md | 2 +-
site2/docs/tiered-storage-gcs.md | 2 +-
.../versioned_docs/version-2.1.0-incubating/reference-configuration.md | 2 +-
.../versioned_docs/version-2.1.1-incubating/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.2.0/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.2.1/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.3.0/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.3.1/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.3.2/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.4.0/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.4.1/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.4.2/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.5.0/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.5.1/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.5.2/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.6.0/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.6.1/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.6.2/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.6.3/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.7.0/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.7.0/tiered-storage-gcs.md | 2 +-
site2/website/versioned_docs/version-2.7.1/reference-configuration.md | 2 +-
site2/website/versioned_docs/version-2.7.1/tiered-storage-gcs.md | 2 +-
23 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/site2/docs/reference-configuration.md
b/site2/docs/reference-configuration.md
index 6bebcc6..ed06774 100644
--- a/site2/docs/reference-configuration.md
+++ b/site2/docs/reference-configuration.md
@@ -272,7 +272,7 @@ subscriptionExpirationTimeMinutes | How long to delete
inactive subscriptions fr
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git a/site2/docs/tiered-storage-gcs.md b/site2/docs/tiered-storage-gcs.md
index b6fec1a..d87ae14 100644
--- a/site2/docs/tiered-storage-gcs.md
+++ b/site2/docs/tiered-storage-gcs.md
@@ -91,7 +91,7 @@ You can configure GCS offloader driver in the configuration
file `broker.conf` o
`gcsManagedLedgerOffloadReadBufferSizeInBytes`|Size of block read|1 MB
`gcsManagedLedgerOffloadMaxBlockSizeInBytes`|Size of block write|64 MB
`managedLedgerMinLedgerRolloverTimeMinutes`|Minimum time between ledger
rollover for a topic.|2
- `managedLedgerMaxEntriesPerLedger`|Max number of entries to append to a
ledger before triggering a rollover.|5000
+ `managedLedgerMaxEntriesPerLedger`|The max number of entries to append to
a ledger before triggering a rollover.|5000
#### Bucket (required)
diff --git
a/site2/website/versioned_docs/version-2.1.0-incubating/reference-configuration.md
b/site2/website/versioned_docs/version-2.1.0-incubating/reference-configuration.md
index e544b5a..df7c3e5 100644
---
a/site2/website/versioned_docs/version-2.1.0-incubating/reference-configuration.md
+++
b/site2/website/versioned_docs/version-2.1.0-incubating/reference-configuration.md
@@ -169,7 +169,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheSizeMB| Amount of memory to use for caching data payload
in managed ledger. This memory is allocated from JVM direct memory and it’s
shared across all the topics running in the same broker |1024|
|managedLedgerCacheEvictionWatermark| Threshold to which bring down the cache
level when eviction is triggered |0.9|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.1.1-incubating/reference-configuration.md
b/site2/website/versioned_docs/version-2.1.1-incubating/reference-configuration.md
index a2e0b59..bd7083c 100644
---
a/site2/website/versioned_docs/version-2.1.1-incubating/reference-configuration.md
+++
b/site2/website/versioned_docs/version-2.1.1-incubating/reference-configuration.md
@@ -169,7 +169,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheSizeMB| Amount of memory to use for caching data payload
in managed ledger. This memory is allocated from JVM direct memory and it’s
shared across all the topics running in the same broker |1024|
|managedLedgerCacheEvictionWatermark| Threshold to which bring down the cache
level when eviction is triggered |0.9|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.2.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.2.0/reference-configuration.md
index 2768648..b4cc121 100644
--- a/site2/website/versioned_docs/version-2.2.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.2.0/reference-configuration.md
@@ -169,7 +169,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheSizeMB| Amount of memory to use for caching data payload
in managed ledger. This memory is allocated from JVM direct memory and it’s
shared across all the topics running in the same broker |1024|
|managedLedgerCacheEvictionWatermark| Threshold to which bring down the cache
level when eviction is triggered |0.9|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger|The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.2.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.2.1/reference-configuration.md
index 09a81ff..887545d 100644
--- a/site2/website/versioned_docs/version-2.2.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.2.1/reference-configuration.md
@@ -175,7 +175,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheSizeMB| Amount of memory to use for caching data payload
in managed ledger. This memory is allocated from JVM direct memory and it’s
shared across all the topics running in the same broker |1024|
|managedLedgerCacheEvictionWatermark| Threshold to which bring down the cache
level when eviction is triggered |0.9|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.3.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.3.0/reference-configuration.md
index c2a6668..e31866a 100644
--- a/site2/website/versioned_docs/version-2.3.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.3.0/reference-configuration.md
@@ -177,7 +177,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheSizeMB| Amount of memory to use for caching data payload
in managed ledger. This memory is allocated from JVM direct memory and it’s
shared across all the topics running in the same broker. By default, uses 1/5th
of available direct memory ||
|managedLedgerCacheEvictionWatermark| Threshold to which bring down the cache
level when eviction is triggered |0.9|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.3.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.3.1/reference-configuration.md
index b70866b..b444385 100644
--- a/site2/website/versioned_docs/version-2.3.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.3.1/reference-configuration.md
@@ -178,7 +178,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheSizeMB| Amount of memory to use for caching data payload
in managed ledger. This memory is allocated from JVM direct memory and it’s
shared across all the topics running in the same broker. By default, uses 1/5th
of available direct memory ||
|managedLedgerCacheEvictionWatermark| Threshold to which bring down the cache
level when eviction is triggered |0.9|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.3.2/reference-configuration.md
b/site2/website/versioned_docs/version-2.3.2/reference-configuration.md
index 1802b4a..ee6e2c5 100644
--- a/site2/website/versioned_docs/version-2.3.2/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.3.2/reference-configuration.md
@@ -184,7 +184,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.4.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.4.0/reference-configuration.md
index e7e7239..386c5f7 100644
--- a/site2/website/versioned_docs/version-2.4.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.4.0/reference-configuration.md
@@ -192,7 +192,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.4.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.4.1/reference-configuration.md
index e7c823b..68470e8 100644
--- a/site2/website/versioned_docs/version-2.4.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.4.1/reference-configuration.md
@@ -192,7 +192,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.4.2/reference-configuration.md
b/site2/website/versioned_docs/version-2.4.2/reference-configuration.md
index 890181a..ee851a6 100644
--- a/site2/website/versioned_docs/version-2.4.2/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.4.2/reference-configuration.md
@@ -192,7 +192,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.5.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.5.0/reference-configuration.md
index dc1ad29..38f998f 100644
--- a/site2/website/versioned_docs/version-2.5.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.5.0/reference-configuration.md
@@ -190,7 +190,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.5.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.5.1/reference-configuration.md
index 1a00788..30a0625 100644
--- a/site2/website/versioned_docs/version-2.5.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.5.1/reference-configuration.md
@@ -197,7 +197,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.5.2/reference-configuration.md
b/site2/website/versioned_docs/version-2.5.2/reference-configuration.md
index 7b63a0b..d0f4a08 100644
--- a/site2/website/versioned_docs/version-2.5.2/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.5.2/reference-configuration.md
@@ -198,7 +198,7 @@ Pulsar brokers are responsible for handling incoming
messages from producers, di
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.6.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.6.0/reference-configuration.md
index 1215771..1af00a1 100644
--- a/site2/website/versioned_docs/version-2.6.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.6.0/reference-configuration.md
@@ -220,7 +220,7 @@ subscriptionExpirationTimeMinutes | How long to delete
inactive subscriptions fr
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger|The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.6.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.6.1/reference-configuration.md
index 764159a..87bf9fc 100644
--- a/site2/website/versioned_docs/version-2.6.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.6.1/reference-configuration.md
@@ -220,7 +220,7 @@ subscriptionExpirationTimeMinutes | How long to delete
inactive subscriptions fr
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.6.2/reference-configuration.md
b/site2/website/versioned_docs/version-2.6.2/reference-configuration.md
index 0a6647b..d44fca3 100644
--- a/site2/website/versioned_docs/version-2.6.2/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.6.2/reference-configuration.md
@@ -221,7 +221,7 @@ subscriptionExpirationTimeMinutes | How long to delete
inactive subscriptions fr
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger|The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.6.3/reference-configuration.md
b/site2/website/versioned_docs/version-2.6.3/reference-configuration.md
index c854b11..a280079 100644
--- a/site2/website/versioned_docs/version-2.6.3/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.6.3/reference-configuration.md
@@ -221,7 +221,7 @@ subscriptionExpirationTimeMinutes | How long to delete
inactive subscriptions fr
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git
a/site2/website/versioned_docs/version-2.7.0/reference-configuration.md
b/site2/website/versioned_docs/version-2.7.0/reference-configuration.md
index 791e164..f2228a1 100644
--- a/site2/website/versioned_docs/version-2.7.0/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.7.0/reference-configuration.md
@@ -273,7 +273,7 @@ subscriptionExpirationTimeMinutes | How long to delete
inactive subscriptions fr
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git a/site2/website/versioned_docs/version-2.7.0/tiered-storage-gcs.md
b/site2/website/versioned_docs/version-2.7.0/tiered-storage-gcs.md
index eadecd0..5ca8503 100644
--- a/site2/website/versioned_docs/version-2.7.0/tiered-storage-gcs.md
+++ b/site2/website/versioned_docs/version-2.7.0/tiered-storage-gcs.md
@@ -92,7 +92,7 @@ You can configure GCS offloader driver in the configuration
file `broker.conf` o
`gcsManagedLedgerOffloadReadBufferSizeInBytes`|Size of block read|1 MB
`gcsManagedLedgerOffloadMaxBlockSizeInBytes`|Size of block write|64 MB
`managedLedgerMinLedgerRolloverTimeMinutes`|Minimum time between ledger
rollover for a topic.|2
- `managedLedgerMaxEntriesPerLedger`|Max number of entries to append to a
ledger before triggering a rollover.|5000
+ `managedLedgerMaxEntriesPerLedger`|The max number of entries to append to
a ledger before triggering a rollover.|5000
#### Bucket (required)
diff --git
a/site2/website/versioned_docs/version-2.7.1/reference-configuration.md
b/site2/website/versioned_docs/version-2.7.1/reference-configuration.md
index 243df91..d90eb7e 100644
--- a/site2/website/versioned_docs/version-2.7.1/reference-configuration.md
+++ b/site2/website/versioned_docs/version-2.7.1/reference-configuration.md
@@ -273,7 +273,7 @@ subscriptionExpirationTimeMinutes | How long to delete
inactive subscriptions fr
|managedLedgerCacheEvictionTimeThresholdMillis| All entries that have stayed
in cache for more than the configured time, will be evicted | 1000 |
|managedLedgerCursorBackloggedThreshold| Configure the threshold (in number of
entries) from where a cursor should be considered 'backlogged' and thus should
be set as inactive. | 1000|
|managedLedgerDefaultMarkDeleteRateLimit| Rate limit the amount of writes per
second generated by consumer acking the messages |1.0|
-|managedLedgerMaxEntriesPerLedger| Max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
max entries have been written to the ledged and at least min-time has
passed</li></ul>|50000|
+|managedLedgerMaxEntriesPerLedger| The max number of entries to append to a
ledger before triggering a rollover. A ledger rollover is triggered on these
conditions: <ul><li>Either the max rollover time has been reached</li><li>or
the max entries have been written to the ledger and at least min-time has
passed</li></ul>|50000|
|managedLedgerMinLedgerRolloverTimeMinutes| Minimum time between ledger
rollover for a topic |10|
|managedLedgerMaxLedgerRolloverTimeMinutes| Maximum time before forcing a
ledger rollover for a topic |240|
|managedLedgerCursorMaxEntriesPerLedger| Max number of entries to append to a
cursor ledger |50000|
diff --git a/site2/website/versioned_docs/version-2.7.1/tiered-storage-gcs.md
b/site2/website/versioned_docs/version-2.7.1/tiered-storage-gcs.md
index fd51229..b82f321 100644
--- a/site2/website/versioned_docs/version-2.7.1/tiered-storage-gcs.md
+++ b/site2/website/versioned_docs/version-2.7.1/tiered-storage-gcs.md
@@ -92,7 +92,7 @@ You can configure GCS offloader driver in the configuration
file `broker.conf` o
`gcsManagedLedgerOffloadReadBufferSizeInBytes`|Size of block read|1 MB
`gcsManagedLedgerOffloadMaxBlockSizeInBytes`|Size of block write|64 MB
`managedLedgerMinLedgerRolloverTimeMinutes`|Minimum time between ledger
rollover for a topic.|2
- `managedLedgerMaxEntriesPerLedger`|Max number of entries to append to a
ledger before triggering a rollover.|5000
+ `managedLedgerMaxEntriesPerLedger`|The max number of entries to append to
a ledger before triggering a rollover.|5000
#### Bucket (required)
