You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by li...@apache.org on 2023/08/01 07:14:23 UTC
[pulsar-site] branch main updated: [improve] [doc] Add compatibility reminders for retry queues (#651)
This is an automated email from the ASF dual-hosted git repository.
liuyu 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 122e648de8b [improve] [doc] Add compatibility reminders for retry queues (#651)
122e648de8b is described below
commit 122e648de8bd6207cafc75012575e6d1268d85e5
Author: fengyubiao <yu...@streamnative.io>
AuthorDate: Tue Aug 1 15:14:18 2023 +0800
[improve] [doc] Add compatibility reminders for retry queues (#651)
---
docs/concepts-messaging.md | 9 +++++++++
versioned_docs/version-2.10.x/concepts-messaging.md | 10 ++++++++++
versioned_docs/version-2.11.x/concepts-messaging.md | 10 ++++++++++
versioned_docs/version-2.8.x/concepts-messaging.md | 4 ++++
versioned_docs/version-2.9.x/concepts-messaging.md | 5 +++++
versioned_docs/version-3.0.x/concepts-messaging.md | 10 ++++++++++
6 files changed, 48 insertions(+)
diff --git a/docs/concepts-messaging.md b/docs/concepts-messaging.md
index 0a72f6e6df9..f89b59412a5 100644
--- a/docs/concepts-messaging.md
+++ b/docs/concepts-messaging.md
@@ -244,6 +244,11 @@ The default retry letter topic uses this format:
<topicname>-<subscriptionname>-RETRY
```
+:::note
+- For Pulsar 2.6.x and 2.7.x, the default retry letter topic uses the format of `<subscriptionname>-RETRY`. If you upgrade from 2.6.x~2.7.x to 2.8.x or later, you need to delete historical retry letter topics and retry letter partitioned topics. Otherwise, Pulsar continues to use original topics, which are formatted with `<subscriptionname>-RETRY`.
+- It is not recommended to use `<subscriptionname>-RETRY` because if multiple topics under the same namespace have the same subscription, then retry message topic names for multiple topics might be the same, which will result in mutual consumptions.
+:::
+
Use the Java client to specify the name of the retry letter topic.
```java
@@ -321,6 +326,10 @@ The default dead letter topic uses this format:
```
<topicname>-<subscriptionname>-DLQ
```
+:::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.
+:::
Use the Java client to specify the name of the dead letter topic.
diff --git a/versioned_docs/version-2.10.x/concepts-messaging.md b/versioned_docs/version-2.10.x/concepts-messaging.md
index 73c46dda567..b8eb5c48e3f 100644
--- a/versioned_docs/version-2.10.x/concepts-messaging.md
+++ b/versioned_docs/version-2.10.x/concepts-messaging.md
@@ -377,6 +377,11 @@ The default retry letter topic uses this format:
```
+:::note
+- For Pulsar 2.6.x and 2.7.x, the default retry letter topic uses the format of `<subscriptionname>-RETRY`. If you upgrade from 2.6.x~2.7.x to 2.8.x or later, you need to delete historical retry letter topics and retry letter partitioned topics. Otherwise, Pulsar continues to use original topics, which are formatted with `<subscriptionname>-RETRY`.
+- It is not recommended to use `<subscriptionname>-RETRY` because if multiple topics under the same namespace have the same subscription, then retry message topic names for multiple topics might be the same, which will result in mutual consumptions.
+:::
+
Use the Java client to specify the name of the retry letter topic.
```java
@@ -466,6 +471,11 @@ 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.
+:::
+
Use the Java client to specify the name of the dead letter topic.
```java
diff --git a/versioned_docs/version-2.11.x/concepts-messaging.md b/versioned_docs/version-2.11.x/concepts-messaging.md
index 29a2bcfb86f..60d63eb53ba 100644
--- a/versioned_docs/version-2.11.x/concepts-messaging.md
+++ b/versioned_docs/version-2.11.x/concepts-messaging.md
@@ -393,6 +393,11 @@ The default retry letter topic uses this format:
<topicname>-<subscriptionname>-RETRY
```
+:::note
+- For Pulsar 2.6.x and 2.7.x, the default retry letter topic uses the format of `<subscriptionname>-RETRY`. If you upgrade from 2.6.x~2.7.x to 2.8.x or later, you need to delete historical retry letter topics and retry letter partitioned topics. Otherwise, Pulsar continues to use original topics, which are formatted with `<subscriptionname>-RETRY`.
+- It is not recommended to use `<subscriptionname>-RETRY` because if multiple topics under the same namespace have the same subscription, then retry message topic names for multiple topics might be the same, which will result in mutual consumptions.
+:::
+
Use the Java client to specify the name of the retry letter topic.
```java
@@ -471,6 +476,11 @@ The default dead letter topic uses this format:
<topicname>-<subscriptionname>-DLQ
```
+:::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.
+:::
+
Use the Java client to specify the name of the dead letter topic.
```java
diff --git a/versioned_docs/version-2.8.x/concepts-messaging.md b/versioned_docs/version-2.8.x/concepts-messaging.md
index 9d130fc4c21..fe0d1330213 100644
--- a/versioned_docs/version-2.8.x/concepts-messaging.md
+++ b/versioned_docs/version-2.8.x/concepts-messaging.md
@@ -231,6 +231,10 @@ 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.
+:::
If you want to specify the name of the dead letter topic, use this Java client example:
diff --git a/versioned_docs/version-2.9.x/concepts-messaging.md b/versioned_docs/version-2.9.x/concepts-messaging.md
index cc0b926bb80..52eea08f367 100644
--- a/versioned_docs/version-2.9.x/concepts-messaging.md
+++ b/versioned_docs/version-2.9.x/concepts-messaging.md
@@ -253,6 +253,11 @@ 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.
+:::
+
If you want to specify the name of the dead letter topic, use this Java client example:
```java
diff --git a/versioned_docs/version-3.0.x/concepts-messaging.md b/versioned_docs/version-3.0.x/concepts-messaging.md
index 4a98f38b15b..d86ea38c877 100644
--- a/versioned_docs/version-3.0.x/concepts-messaging.md
+++ b/versioned_docs/version-3.0.x/concepts-messaging.md
@@ -244,6 +244,11 @@ The default retry letter topic uses this format:
<topicname>-<subscriptionname>-RETRY
```
+:::note
+- For Pulsar 2.6.x and 2.7.x, the default retry letter topic uses the format of `<subscriptionname>-RETRY`. If you upgrade from 2.6.x~2.7.x to 2.8.x or later, you need to delete historical retry letter topics and retry letter partitioned topics. Otherwise, Pulsar continues to use original topics, which are formatted with `<subscriptionname>-RETRY`.
+- It is not recommended to use `<subscriptionname>-RETRY` because if multiple topics under the same namespace have the same subscription, then retry message topic names for multiple topics might be the same, which will result in mutual consumptions.
+:::
+
Use the Java client to specify the name of the retry letter topic.
```java
@@ -322,6 +327,11 @@ The default dead letter topic uses this format:
<topicname>-<subscriptionname>-DLQ
```
+:::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.
+:::
+
Use the Java client to specify the name of the dead letter topic.
```java