lhotari opened a new issue, #25277: URL: https://github.com/apache/pulsar/issues/25277
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [x] I understand that [unsupported versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions) don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### User environment master branch ### Issue Description There's a log message `log.warn("[{}] Draining hash {} not found in the tracker for consumer {}", dispatcherName, hash, consumer);` here: https://github.com/apache/pulsar/blob/d992dc530bea4f4737da93f1527133b1c9389a45/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/DrainingHashesTracker.java#L188 Initially in the PIP-379, the stats were strongly consistent with the draining hashes state. This caused dead locks and the deadlock was fixed in #23854. The warning log no longer makes sense and should be changed to debug logging. ### Error messages ```text ``` ### Reproducing the issue n/a ### Additional information _No response_ ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
