You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "TTMickael (via GitHub)" <gi...@apache.org> on 2023/07/28 12:10:07 UTC

[GitHub] [pulsar] TTMickael opened a new issue, #20899: [Bug]

TTMickael opened a new issue, #20899:
URL: https://github.com/apache/pulsar/issues/20899

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
   
   
   ### Version
   
   3.0.0
   
   ### Minimal reproduce step
   
   Have a partitioned topic
   Create a Key_Shared subscription
   Produce one message with a key X
   Consume one message with the key X but do never ack it
   Produce a second message with a key X
   
   ### What did you expect to see?
   
   The second message is not pushed by the broker
   
   ### What did you see instead?
   
   The second message is consumed
   
   ### Anything else?
   
   This behavior has been observed after migrating from 2.10.1 to 3.0.0
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
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.apache.org

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

[GitHub] [pulsar] poorbarcode commented on issue #20899: [Bug] Broker dispatch messages despite a message with the same key is unack

Posted by "poorbarcode (via GitHub)" <gi...@apache.org>.
poorbarcode commented on issue #20899:
URL: https://github.com/apache/pulsar/issues/20899#issuecomment-1663253557

   @TTMickael 
   
   > Have a partitioned topic
   > Create a Key_Shared subscription
   > Produce one message with a key X
   > Consume one message with the key X but do never ack it
   > Produce a second message with a key X
   
   Is there only one consumer to consume messages? If yes, it is an expected behavior


-- 
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

[GitHub] [pulsar] TTMickael commented on issue #20899: [Bug] Broker dispatch messages despite a message with the same key is unack

Posted by "TTMickael (via GitHub)" <gi...@apache.org>.
TTMickael commented on issue #20899:
URL: https://github.com/apache/pulsar/issues/20899#issuecomment-1670914428

   We have 2 consumers for this subscription. I'm expecting in any case that messages with the same key won't be dispatched to ensure the order of delivery unless the unacked message get acked. Am I wrong?


-- 
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: [I] [Bug] Broker dispatch messages despite a message with the same key is unack [pulsar]

Posted by "Denovo1998 (via GitHub)" <gi...@apache.org>.
Denovo1998 commented on issue #20899:
URL: https://github.com/apache/pulsar/issues/20899#issuecomment-1817538103

   @TTMickael @poorbarcode 
   Maybe the first consumer without ack message was closed after sending a second message with the same key?
   
   ![CleanShot 2023-11-18 at 23 22 31@2x](https://github.com/apache/pulsar/assets/54846009/6175874f-1d3b-431e-b2f6-fd9acd22ecd5)
   


-- 
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

[GitHub] [pulsar] github-actions[bot] commented on issue #20899: [Bug] Broker dispatch messages despite a message with the same key is unack

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #20899:
URL: https://github.com/apache/pulsar/issues/20899#issuecomment-1712380143

   The issue had no activity for 30 days, mark with Stale label.


-- 
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