-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fix][test] flaky test ManagedLedgerBkTest.asyncMarkDeleteAndClose #18362
[fix][test] flaky test ManagedLedgerBkTest.asyncMarkDeleteAndClose #18362
Conversation
4db61d1
to
76abd0e
Compare
Codecov Report
@@ Coverage Diff @@
## master #18362 +/- ##
============================================
- Coverage 47.15% 47.12% -0.03%
+ Complexity 10432 10411 -21
============================================
Files 697 698 +1
Lines 68023 67986 -37
Branches 7284 7271 -13
============================================
- Hits 32074 32041 -33
- Misses 32367 32400 +33
+ Partials 3582 3545 -37
Flags with carried forward coverage won't be shown. Click here to find out more.
|
/pulsarbot rerun-failure-checks |
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.
Although I suspect we may not retry on failure, the change is OK to merge.
76abd0e
to
fd24928
Compare
Fixes #16729
Motivation
same as #18310
ManagedCursorImpl
has a known problem: when thecursor.close
and thecursor.switchLedger
are concurrent executing, a bad version exception is thrown. see:pulsar/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedCursorImpl.java
Lines 2595 to 2619 in 0c3c175
Modifications
managedLedger.close
triggers thecursor.close
, so remove codecursor.close
managedLedger.close
fail, just retry, it will be okDocumentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: