This is an automated email from the ASF dual-hosted git repository.
zike 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 1f6dde23f1e9 Add note about 2.x dlq has a default 30s ackTimeout
policy in messaging.md (#985)
1f6dde23f1e9 is described below
commit 1f6dde23f1e94b217bccf28684e9e9969605f7e9
Author: zhou zhuohan <[email protected]>
AuthorDate: Fri Feb 14 17:17:16 2025 +0800
Add note about 2.x dlq has a default 30s ackTimeout policy in messaging.md
(#985)
---
docs/concepts-messaging.md | 1 +
versioned_docs/version-3.0.x/concepts-messaging.md | 1 +
versioned_docs/version-3.3.x/concepts-messaging.md | 1 +
versioned_docs/version-4.0.x/concepts-messaging.md | 1 +
4 files changed, 4 insertions(+)
diff --git a/docs/concepts-messaging.md b/docs/concepts-messaging.md
index ffdecf841adc..bd80f146a74d 100644
--- a/docs/concepts-messaging.md
+++ b/docs/concepts-messaging.md
@@ -344,6 +344,7 @@ The dead letter producerName uses this format:
:::note
- For Pulsar 2.6.x and 2.7.x, the default dead letter topic uses the format of
`<subscriptionname>-DLQ`. If you upgrade from 2.6.x~2.7.x to 2.8.x or later,
you need to delete historical dead letter topics and retry letter partitioned
topics. Otherwise, Pulsar continues to use original topics, which are formatted
with `<subscriptionname>-DLQ`.
- It is not recommended to use `<subscriptionname>-DLQ` because if multiple
topics under the same namespace have the same subscription, then dead message
topic names for multiple topics might be the same, which will result in mutual
consumptions.
+- From Pulsar 2.3.x to 2.10.x, Java SDK dead letter policy will set a 30
seconds acknowledgment timeout when there is no user defined acknowledgment
timeout. This default timeout policy has been removed since 3.0.x.
:::
Use the Java client to specify the name of the dead letter topic.
diff --git a/versioned_docs/version-3.0.x/concepts-messaging.md
b/versioned_docs/version-3.0.x/concepts-messaging.md
index 924a455b6af9..958968eb1bb0 100644
--- a/versioned_docs/version-3.0.x/concepts-messaging.md
+++ b/versioned_docs/version-3.0.x/concepts-messaging.md
@@ -330,6 +330,7 @@ The default dead letter topic uses this format:
:::note
- For Pulsar 2.6.x and 2.7.x, the default dead letter topic uses the format of
`<subscriptionname>-DLQ`. If you upgrade from 2.6.x~2.7.x to 2.8.x or later,
you need to delete historical dead letter topics and retry letter partitioned
topics. Otherwise, Pulsar continues to use original topics, which are formatted
with `<subscriptionname>-DLQ`.
- It is not recommended to use `<subscriptionname>-DLQ` because if multiple
topics under the same namespace have the same subscription, then dead message
topic names for multiple topics might be the same, which will result in mutual
consumptions.
+- From Pulsar 2.3.x to 2.10.x, Java SDK dead letter policy will set a 30
seconds acknowledgment timeout when there is no user defined acknowledgment
timeout. This default timeout policy has been removed since 3.0.x.
:::
Use the Java client to specify the name of the dead letter topic.
diff --git a/versioned_docs/version-3.3.x/concepts-messaging.md
b/versioned_docs/version-3.3.x/concepts-messaging.md
index 19254fea174d..a3f4217f746f 100644
--- a/versioned_docs/version-3.3.x/concepts-messaging.md
+++ b/versioned_docs/version-3.3.x/concepts-messaging.md
@@ -342,6 +342,7 @@ The dead letter producerName uses this format:
:::note
- For Pulsar 2.6.x and 2.7.x, the default dead letter topic uses the format of
`<subscriptionname>-DLQ`. If you upgrade from 2.6.x~2.7.x to 2.8.x or later,
you need to delete historical dead letter topics and retry letter partitioned
topics. Otherwise, Pulsar continues to use original topics, which are formatted
with `<subscriptionname>-DLQ`.
- It is not recommended to use `<subscriptionname>-DLQ` because if multiple
topics under the same namespace have the same subscription, then dead message
topic names for multiple topics might be the same, which will result in mutual
consumptions.
+- From Pulsar 2.3.x to 2.10.x, Java SDK dead letter policy will set a 30
seconds acknowledgment timeout when there is no user defined acknowledgment
timeout. This default timeout policy has been removed since 3.0.x.
:::
Use the Java client to specify the name of the dead letter topic.
diff --git a/versioned_docs/version-4.0.x/concepts-messaging.md
b/versioned_docs/version-4.0.x/concepts-messaging.md
index 36988bbe46f3..63b55604e7e3 100644
--- a/versioned_docs/version-4.0.x/concepts-messaging.md
+++ b/versioned_docs/version-4.0.x/concepts-messaging.md
@@ -342,6 +342,7 @@ The dead letter producerName uses this format:
:::note
- For Pulsar 2.6.x and 2.7.x, the default dead letter topic uses the format of
`<subscriptionname>-DLQ`. If you upgrade from 2.6.x~2.7.x to 2.8.x or later,
you need to delete historical dead letter topics and retry letter partitioned
topics. Otherwise, Pulsar continues to use original topics, which are formatted
with `<subscriptionname>-DLQ`.
- It is not recommended to use `<subscriptionname>-DLQ` because if multiple
topics under the same namespace have the same subscription, then dead message
topic names for multiple topics might be the same, which will result in mutual
consumptions.
+- From Pulsar 2.3.x to 2.10.x, Java SDK dead letter policy will set a 30
seconds acknowledgment timeout when there is no user defined acknowledgment
timeout. This default timeout policy has been removed since 3.0.x.
:::
Use the Java client to specify the name of the dead letter topic.
