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 453acab89289 [doc] Add a note: if using Delayed messages, advisable to
exercise caution when using the Backlog Quota strategy (#771)
453acab89289 is described below
commit 453acab8928901442d8a0171248cd4fb18f2f830
Author: fengyubiao <[email protected]>
AuthorDate: Wed Jan 17 09:18:08 2024 +0800
[doc] Add a note: if using Delayed messages, advisable to exercise caution
when using the Backlog Quota strategy (#771)
---
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, 25 insertions(+), 5 deletions(-)
diff --git a/docs/concepts-messaging.md b/docs/concepts-messaging.md
index c47c0f8160c2..c9f409a93179 100644
--- a/docs/concepts-messaging.md
+++ b/docs/concepts-messaging.md
@@ -1193,7 +1193,11 @@ A broker saves a message without any check. When a
consumer consumes a message,
:::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.
+Work with retention policy: 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 subse [...]
+
+Work with backlog quota policy: After using delayed messages, it is advisable
to exercise caution when using the Backlog Quota strategy. This is because
delayed messages can result in not being consumed for an extended period,
triggering the Backlog Quota strategy and causing subsequent message sends to
be rejected.
+
+Work with backlog TTL policy: When the TTL expires, Pulsar automatically moves
the message to the acknowledged state (and thus makes it ready for deletion)
even if the messages are delayed messages and does not care about when the
expected delayed time is.
:::
diff --git a/versioned_docs/version-2.10.x/concepts-messaging.md
b/versioned_docs/version-2.10.x/concepts-messaging.md
index 4ce4ff509188..713a2d64060c 100644
--- a/versioned_docs/version-2.10.x/concepts-messaging.md
+++ b/versioned_docs/version-2.10.x/concepts-messaging.md
@@ -990,7 +990,11 @@ A broker saves a message without any check. When a
consumer consumes a message,
:::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.
+Work with retention policy: 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 subse [...]
+
+Work with backlog quota policy: After using delayed messages, it is advisable
to exercise caution when using the Backlog Quota strategy. This is because
delayed messages can result in not being consumed for an extended period,
triggering the Backlog Quota strategy and causing subsequent message sends to
be rejected.
+
+Work with backlog TTL policy: When the TTL expires, Pulsar automatically moves
the message to the acknowledged state (and thus makes it ready for deletion)
even if the messages are delayed messages and does not care about when the
expected delayed time is.
:::
diff --git a/versioned_docs/version-2.11.x/concepts-messaging.md
b/versioned_docs/version-2.11.x/concepts-messaging.md
index 0d1a5ffcc336..4a8d22cc826d 100644
--- a/versioned_docs/version-2.11.x/concepts-messaging.md
+++ b/versioned_docs/version-2.11.x/concepts-messaging.md
@@ -1145,7 +1145,11 @@ A broker saves a message without any check. When a
consumer consumes a message,
:::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.
+Work with retention policy: 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 subse [...]
+
+Work with backlog quota policy: After using delayed messages, it is advisable
to exercise caution when using the Backlog Quota strategy. This is because
delayed messages can result in not being consumed for an extended period,
triggering the Backlog Quota strategy and causing subsequent message sends to
be rejected.
+
+Work with backlog TTL policy: When the TTL expires, Pulsar automatically moves
the message to the acknowledged state (and thus makes it ready for deletion)
even if the messages are delayed messages and does not care about when the
expected delayed time is.
:::
diff --git a/versioned_docs/version-3.0.x/concepts-messaging.md
b/versioned_docs/version-3.0.x/concepts-messaging.md
index ee368df5ebf5..f7cba02aab24 100644
--- a/versioned_docs/version-3.0.x/concepts-messaging.md
+++ b/versioned_docs/version-3.0.x/concepts-messaging.md
@@ -1142,7 +1142,11 @@ A broker saves a message without any check. When a
consumer consumes a message,
:::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.
+Work with retention policy: 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 subse [...]
+
+Work with backlog quota policy: After using delayed messages, it is advisable
to exercise caution when using the Backlog Quota strategy. This is because
delayed messages can result in not being consumed for an extended period,
triggering the Backlog Quota strategy and causing subsequent message sends to
be rejected.
+
+Work with backlog TTL policy: When the TTL expires, Pulsar automatically moves
the message to the acknowledged state (and thus makes it ready for deletion)
even if the messages are delayed messages and does not care about when the
expected delayed time is.
:::
diff --git a/versioned_docs/version-3.1.x/concepts-messaging.md
b/versioned_docs/version-3.1.x/concepts-messaging.md
index 7fb6682db523..e818cb884e7e 100644
--- a/versioned_docs/version-3.1.x/concepts-messaging.md
+++ b/versioned_docs/version-3.1.x/concepts-messaging.md
@@ -1162,7 +1162,11 @@ A broker saves a message without any check. When a
consumer consumes a message,
:::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.
+Work with retention policy: 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 subse [...]
+
+Work with backlog quota policy: After using delayed messages, it is advisable
to exercise caution when using the Backlog Quota strategy. This is because
delayed messages can result in not being consumed for an extended period,
triggering the Backlog Quota strategy and causing subsequent message sends to
be rejected.
+
+Work with backlog TTL policy: When the TTL expires, Pulsar automatically moves
the message to the acknowledged state (and thus makes it ready for deletion)
even if the messages are delayed messages and does not care about when the
expected delayed time is.
:::
