You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "poorbarcode (via GitHub)" <gi...@apache.org> on 2024/01/14 16:27:26 UTC

[PR] [doc] Add a note: if using Delayed messages, advisable to exercise caution when using the Backlog Quota strategy [pulsar-site]

poorbarcode opened a new pull request, #771:
URL: https://github.com/apache/pulsar-site/pull/771

   After using delayed messages, it is advisable to exercise caution when using the Backlog Quota strategy.  This is because delayed messages can result in messages not being consumed for an extended period, triggering the Backlog Quota strategy and causing subsequent message sends to be rejected.
   
   This PR fixes #xyz 
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [x] `doc` <!-- Your PR contains doc changes. Please attach the local preview screenshots (run `./preview.sh` at root path) to your PR description, or else your PR might not get merged. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update later -->
   - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [doc] Add a note: if using Delayed messages, advisable to exercise caution when using the Backlog Quota strategy [pulsar-site]

Posted by "poorbarcode (via GitHub)" <gi...@apache.org>.
poorbarcode commented on PR #771:
URL: https://github.com/apache/pulsar-site/pull/771#issuecomment-1892603729

   A picture for preview
   
   <img width="976" alt="Screenshot 2024-01-16 at 02 09 57" src="https://github.com/apache/pulsar-site/assets/25195800/4212c963-5aed-4328-ad25-bef2f90501af">
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [doc] Add a note: if using Delayed messages, advisable to exercise caution when using the Backlog Quota strategy [pulsar-site]

Posted by "codelipenghui (via GitHub)" <gi...@apache.org>.
codelipenghui commented on code in PR #771:
URL: https://github.com/apache/pulsar-site/pull/771#discussion_r1451843464


##########
docs/concepts-messaging.md:
##########
@@ -1193,7 +1193,7 @@ 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.
+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. After using delayed messages, it is advisable to exercise caution when using the Backlog Quota strategy.  This is because delayed messages can result in messages not being consumed for an extended period, triggering the Backlog Quota strategy and causing subsequent message sends to be rejected.

Review Comment:
   @poorbarcode I think we should have 3 paragraphs for explaining the data retention, backlog, and message TTL work with delayed messages.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [doc] Add a note: if using Delayed messages, advisable to exercise caution when using the Backlog Quota strategy [pulsar-site]

Posted by "poorbarcode (via GitHub)" <gi...@apache.org>.
poorbarcode commented on code in PR #771:
URL: https://github.com/apache/pulsar-site/pull/771#discussion_r1452646618


##########
docs/concepts-messaging.md:
##########
@@ -1193,7 +1193,7 @@ 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.
+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. After using delayed messages, it is advisable to exercise caution when using the Backlog Quota strategy.  This is because delayed messages can result in messages not being consumed for an extended period, triggering the Backlog Quota strategy and causing subsequent message sends to be rejected.

Review Comment:
   Done



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] [doc] Add a note: if using Delayed messages, advisable to exercise caution when using the Backlog Quota strategy [pulsar-site]

Posted by "codelipenghui (via GitHub)" <gi...@apache.org>.
codelipenghui merged PR #771:
URL: https://github.com/apache/pulsar-site/pull/771


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org