-
Notifications
You must be signed in to change notification settings - Fork 138
[transactions] Reduce spammy log during broker shutdown #1896
base: master
Are you sure you want to change the base?
[transactions] Reduce spammy log during broker shutdown #1896
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1896 +/- ##
============================================
- Coverage 18.77% 18.77% -0.01%
Complexity 743 743
============================================
Files 184 184
Lines 13289 13292 +3
Branches 1211 1213 +2
============================================
Hits 2495 2495
- Misses 10613 10616 +3
Partials 181 181
|
if (throwable instanceof PulsarClientException.LookupException | ||
|| throwable.getCause() instanceof PulsarClientException.LookupException) { | ||
log.warn("Failed to find broker for topic partition {} - {}", topicPartition, | ||
throwable + ""); | ||
} else { | ||
log.warn("Failed to find broker for topic partition {}", topicPartition, throwable); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How could it reduce the spammy logs? For the lookup exception, there are still warn logs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but when the cause is LookupException
, it won't print the stack info.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it won't print the stack info.
I think not. See line 335, it's still log.warn
.
Motivation
Reduce spammy log during broker shutdown
Documentation
Check the box below.
Need to update docs?
doc-required
(If you need help on updating docs, create a doc issue)
no-need-doc
(Please explain why)
doc
(If this PR contains doc changes)