You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/06/03 14:45:35 UTC

[GitHub] [pulsar] merlimat commented on pull request #7106: Fixed ordering issue in KeyShared dispatcher when adding consumer

merlimat commented on pull request #7106:
URL: https://github.com/apache/pulsar/pull/7106#issuecomment-638245810


   > The buffer is still possible to break the message order dispatching of the same key. It is better not to add the buffer at present.
   
   Yes, that was my thought. To guarantee the ordering we need for these consumers to wait for that messages to be acked before start consuming.
   
   On top of this I also have one more change with a setting for `allowOutOfOrderDelivery`. In some cases, an application might not need strict ordering, rather just the "stickiness" of keys to the same consumer. In this scenario, we can relax the ordering requirement and basically we skip the `recentlyJoinedConsumers` alltogether.


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

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