mattisonchao commented on issue #21045: URL: https://github.com/apache/pulsar/issues/21045#issuecomment-1689423900
The `KEY_SHARE` mode is a somewhat strict pulsar type. that is very sensitive to the consumption(acknowledgement) rate since it should ensure the [message order](https://streamnative.io/blog/scalable-stream-processing-pulsars-key-shared-subscription#:~:text=Unlike%20traditional%20messaging%20where%20any,delivered%20to%20the%20same%20consumer.). Therefore, It's expected behaviour. You can check why some of your consumers can't catch up or consider If you can try to use another subscription mode like `SHARED`. But anyway. You are right. We should have a limit on this container's memory usage to avoid one topic affecting the whole broker. :) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
