-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Open
Labels
type/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug
Description
Search before reporting
- I searched in the issues and found nothing similar.
Read release policy
- I understand that unsupported 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:
pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/DrainingHashesTracker.java
Line 188 in d992dc5
| log.warn("[{}] Draining hash {} not found in the tracker for consumer {}", dispatcherName, hash, |
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
Reproducing the issue
n/a
Additional information
No response
Are you willing to submit a PR?
- I'm willing to submit a PR!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
type/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug