[fix][broker] Fix compaction service log's wrong condition - #24207
Conversation
|
/pulsarbot rerun-failure-checks |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #24207 +/- ##
============================================
+ Coverage 73.57% 74.25% +0.67%
+ Complexity 32624 32528 -96
============================================
Files 1877 1865 -12
Lines 139502 144659 +5157
Branches 15299 16523 +1224
============================================
+ Hits 102638 107410 +4772
+ Misses 28908 28757 -151
- Partials 7956 8492 +536
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
lhotari
left a comment
There was a problem hiding this comment.
The change itself is ok, but the title and description of the PR are not describing the relevant context of the change:
- The impact isn't described at all. The impact seems to be that there would be invalid error logs for every compaction. Is that correct?
- This change is a follow up on #23980 changes that haven't been released yet. It would be useful to mention this in the description that this is a follow up on #23980 changes.
Correct, Updated in the Motivation |
(cherry picked from commit bc9306f)
(cherry picked from commit bc9306f)
(cherry picked from commit bc9306f)
) (cherry picked from commit bc9306f)
Motivation
background
CompactedTopicImpl.newCompactedLedgerwas called more than once with the samecompactedLedgerId, it will trigger a ledger deletion, which causes a data loss event.Issue
previousLedger == @param-newLedger, but it is@param-newLedger == @param-newLedgerModifications
Fix the wrong condition of printing error log
Documentation
docdoc-requireddoc-not-neededdoc-completeMatching PR in forked repository
PR in forked repository: x