I suggest you keep a prefetch lower than max-read.. just to be on a safe side
avoiding some false log.warn calls that would happen for too many credits
issues from consumers.
On 2025/01/23 06:23:05 s.go...@inform-technology.de wrote:
> Okay, I think I have understood the difference. As we tend
As I showed on the code, there will be a log.warn if max-read is reached.
You would need really a client consuming messages and not doing any acks to
reach the limit.
You can find this on the web console by monitoring delivering and asked metrics.
One rule of thumb I have used is to keep abou
Okay, I think I have understood the difference. As we tend to have very small
transactions or immediate commits this will not make much of a difference in
our use case.
Last question:
The example you showed demonstrates how to starve the client,because of the
limit in max-read/prefetch. In a rea
