Search before reporting
Read release policy
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:
|
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?
Search before reporting
Read release policy
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
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?