wolfstudy commented on pull request #14950: URL: https://github.com/apache/pulsar/pull/14950#issuecomment-1083226008
> I believe in this case the log should really be at debug level. The information is already available in the topic stats for debugging purposes. Yes, when the unack reaches the maximum threshold, we can get the number of unackedMessages through `pulsar-admin topics stats`, and get the maxUnackedMessage threshold from `pulsar-admin namespace policies`. But when this threshold is triggered, **Dispatcher read is blocked**. This behavior is actively triggered by the broker, which is not transparent enough to the client-side. We still need a more intuitive form to quickly locate this problem. It seems a reasonable way to output the specified log information to the broker log file. -- 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]
