-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[fix] [log] Do not print warn log when concurrently publishing and switching ledgers #23209
Conversation
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.
LGTM
It's necessary to cherry-pick to the branches where #22221 exists. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #23209 +/- ##
============================================
+ Coverage 73.57% 74.52% +0.94%
- Complexity 32624 33656 +1032
============================================
Files 1877 1918 +41
Lines 139502 144628 +5126
Branches 15299 15812 +513
============================================
+ Hits 102638 107781 +5143
+ Misses 28908 28588 -320
- Partials 7956 8259 +303
Flags with carried forward coverage won't be shown. Click here to find out more.
|
…itching ledgers (apache#23209) (cherry picked from commit 0a5cb51) (cherry picked from commit 57b0ca4)
…itching ledgers (apache#23209) (cherry picked from commit 0a5cb51) (cherry picked from commit 57b0ca4)
Fixes #23208
Main Issue: #23208
Motivation & Modifications
When
publishing
andledger switching
execute concurrently, the broker will print a warn-level logAn OpAddEntry's ledger is empty.
, but it should not be awarn
level. The testtestConcurrentlyOfPublishAndSwitchLedger
can reproduce the warning log printing.Documentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: x