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 cf0f49046cd6 Docs sync done from apache/pulsar (#04e89fe)
cf0f49046cd6 is described below
commit cf0f49046cd60fc9dcfe008320e1d8aeeaeb6a1d
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Fri Jan 10 01:36:16 2025 +0000
Docs sync done from apache/pulsar (#04e89fe)
---
.../reference/next/config/reference-configuration-broker.md | 11 +++++++++++
.../next/config/reference-configuration-standalone.md | 11 +++++++++++
2 files changed, 22 insertions(+)
diff --git a/static/reference/next/config/reference-configuration-broker.md
b/static/reference/next/config/reference-configuration-broker.md
index 15017675ec2e..3f12dc5dbe71 100644
--- a/static/reference/next/config/reference-configuration-broker.md
+++ b/static/reference/next/config/reference-configuration-broker.md
@@ -5029,6 +5029,17 @@ How frequently to flush the cursor positions that were
accumulated due to rate l
**Category**: Storage (Managed Ledger)
+### managedLedgerCursorResetLedgerCloseTimestampMaxClockSkewMillis
+When resetting a subscription by timestamp, the broker will use the ledger
closing timestamp metadata to determine the range of ledgers to search for the
message where the subscription position is reset to. Since by default, the
search condition is based on the message publish time provided by the client
at the publish time, there will be some clock skew between the ledger closing
timestamp metadata and the publish time. This configuration is used to set the
max clock skew between the [...]
+
+**Type**: `int`
+
+**Default**: `60000`
+
+**Dynamic**: `true`
+
+**Category**: Storage (Managed Ledger)
+
### managedLedgerCursorRolloverTimeInSeconds
Max time before triggering a rollover on a cursor ledger
diff --git a/static/reference/next/config/reference-configuration-standalone.md
b/static/reference/next/config/reference-configuration-standalone.md
index 15017675ec2e..3f12dc5dbe71 100644
--- a/static/reference/next/config/reference-configuration-standalone.md
+++ b/static/reference/next/config/reference-configuration-standalone.md
@@ -5029,6 +5029,17 @@ How frequently to flush the cursor positions that were
accumulated due to rate l
**Category**: Storage (Managed Ledger)
+### managedLedgerCursorResetLedgerCloseTimestampMaxClockSkewMillis
+When resetting a subscription by timestamp, the broker will use the ledger
closing timestamp metadata to determine the range of ledgers to search for the
message where the subscription position is reset to. Since by default, the
search condition is based on the message publish time provided by the client
at the publish time, there will be some clock skew between the ledger closing
timestamp metadata and the publish time. This configuration is used to set the
max clock skew between the [...]
+
+**Type**: `int`
+
+**Default**: `60000`
+
+**Dynamic**: `true`
+
+**Category**: Storage (Managed Ledger)
+
### managedLedgerCursorRolloverTimeInSeconds
Max time before triggering a rollover on a cursor ledger
