This is an automated email from the ASF dual-hosted git repository.
penghui 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 1da3ea44db84 [doc] Avoid users send messages with too long delay time
(#764)
1da3ea44db84 is described below
commit 1da3ea44db845e5e47abf7a293866bbb7ea50aed
Author: fengyubiao <[email protected]>
AuthorDate: Wed Jan 10 08:15:15 2024 +0800
[doc] Avoid users send messages with too long delay time (#764)
---
docs/concepts-messaging.md | 6 ++++++
versioned_docs/version-2.10.x/concepts-messaging.md | 6 ++++++
versioned_docs/version-2.11.x/concepts-messaging.md | 6 ++++++
versioned_docs/version-3.0.x/concepts-messaging.md | 6 ++++++
versioned_docs/version-3.1.x/concepts-messaging.md | 6 ++++++
5 files changed, 30 insertions(+)
diff --git a/docs/concepts-messaging.md b/docs/concepts-messaging.md
index 0249c4b6ccf7..c47c0f8160c2 100644
--- a/docs/concepts-messaging.md
+++ b/docs/concepts-messaging.md
@@ -1191,6 +1191,12 @@ The diagram below illustrates the concept of delayed
message delivery:
A broker saves a message without any check. When a consumer consumes a
message, if the message is set to delay, then the message is added to
`DelayedDeliveryTracker`. A subscription checks and gets timeout messages from
`DelayedDeliveryTracker`.
+:::note
+
+In Pulsar, the ledger will be deleted automatically after the messages in this
ledger have been consumed. Pulsar will delete the front ledgers of a topic but
will not delete ledgers from the middle of a topic. It means that if you send a
message that is delayed for a long time, the message will not be consumed until
it reaches the delay time. This means all the ledgers on this topic could not
be deleted until the delayed message is consumed, even if some subsequent
ledgers are fully consumed.
+
+:::
+
### Broker
Delayed message delivery is enabled by default. You can change it in the
broker configuration file as below:
diff --git a/versioned_docs/version-2.10.x/concepts-messaging.md
b/versioned_docs/version-2.10.x/concepts-messaging.md
index b8eb5c48e3f1..4ce4ff509188 100644
--- a/versioned_docs/version-2.10.x/concepts-messaging.md
+++ b/versioned_docs/version-2.10.x/concepts-messaging.md
@@ -988,6 +988,12 @@ The diagram below illustrates the concept of delayed
message delivery:
A broker saves a message without any check. When a consumer consumes a
message, if the message is set to delay, then the message is added to
`DelayedDeliveryTracker`. A subscription checks and gets timeout messages from
`DelayedDeliveryTracker`.
+:::note
+
+In Pulsar, the ledger will be deleted automatically after the messages in this
ledger have been consumed. Pulsar will delete the front ledgers of a topic but
will not delete ledgers from the middle of a topic. It means that if you send a
message that is delayed for a long time, the message will not be consumed until
it reaches the delay time. This means all the ledgers on this topic could not
be deleted until the delayed message is consumed, even if some subsequent
ledgers are fully consumed.
+
+:::
+
### Broker
Delayed message delivery is enabled by default. You can change it in the
broker configuration file as below:
diff --git a/versioned_docs/version-2.11.x/concepts-messaging.md
b/versioned_docs/version-2.11.x/concepts-messaging.md
index 60d63eb53bac..0d1a5ffcc336 100644
--- a/versioned_docs/version-2.11.x/concepts-messaging.md
+++ b/versioned_docs/version-2.11.x/concepts-messaging.md
@@ -1143,6 +1143,12 @@ The diagram below illustrates the concept of delayed
message delivery:
A broker saves a message without any check. When a consumer consumes a
message, if the message is set to delay, then the message is added to
`DelayedDeliveryTracker`. A subscription checks and gets timeout messages from
`DelayedDeliveryTracker`.
+:::note
+
+In Pulsar, the ledger will be deleted automatically after the messages in this
ledger have been consumed. Pulsar will delete the front ledgers of a topic but
will not delete ledgers from the middle of a topic. It means that if you send a
message that is delayed for a long time, the message will not be consumed until
it reaches the delay time. This means all the ledgers on this topic could not
be deleted until the delayed message is consumed, even if some subsequent
ledgers are fully consumed.
+
+:::
+
### Broker
Delayed message delivery is enabled by default. You can change it in the
broker configuration file as below:
diff --git a/versioned_docs/version-3.0.x/concepts-messaging.md
b/versioned_docs/version-3.0.x/concepts-messaging.md
index d86ea38c8776..ee368df5ebf5 100644
--- a/versioned_docs/version-3.0.x/concepts-messaging.md
+++ b/versioned_docs/version-3.0.x/concepts-messaging.md
@@ -1140,6 +1140,12 @@ The diagram below illustrates the concept of delayed
message delivery:
A broker saves a message without any check. When a consumer consumes a
message, if the message is set to delay, then the message is added to
`DelayedDeliveryTracker`. A subscription checks and gets timeout messages from
`DelayedDeliveryTracker`.
+:::note
+
+In Pulsar, the ledger will be deleted automatically after the messages in this
ledger have been consumed. Pulsar will delete the front ledgers of a topic but
will not delete ledgers from the middle of a topic. It means that if you send a
message that is delayed for a long time, the message will not be consumed until
it reaches the delay time. This means all the ledgers on this topic could not
be deleted until the delayed message is consumed, even if some subsequent
ledgers are fully consumed.
+
+:::
+
### Broker
Delayed message delivery is enabled by default. You can change it in the
broker configuration file as below:
diff --git a/versioned_docs/version-3.1.x/concepts-messaging.md
b/versioned_docs/version-3.1.x/concepts-messaging.md
index f89b59412a50..7fb6682db523 100644
--- a/versioned_docs/version-3.1.x/concepts-messaging.md
+++ b/versioned_docs/version-3.1.x/concepts-messaging.md
@@ -1160,6 +1160,12 @@ The diagram below illustrates the concept of delayed
message delivery:
A broker saves a message without any check. When a consumer consumes a
message, if the message is set to delay, then the message is added to
`DelayedDeliveryTracker`. A subscription checks and gets timeout messages from
`DelayedDeliveryTracker`.
+:::note
+
+In Pulsar, the ledger will be deleted automatically after the messages in this
ledger have been consumed. Pulsar will delete the front ledgers of a topic but
will not delete ledgers from the middle of a topic. It means that if you send a
message that is delayed for a long time, the message will not be consumed until
it reaches the delay time. This means all the ledgers on this topic could not
be deleted until the delayed message is consumed, even if some subsequent
ledgers are fully consumed.
+
+:::
+
### Broker
Delayed message delivery is enabled by default. You can change it in the
broker configuration file as below:
