[branch-2.9] Fix no durable cursor leak problem #18710
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gaozhangmin
requested review from
codelipenghui,
eolivelli and
zymap
and removed request for
codelipenghui,
eolivelli and
zymap
BewareMyPower
approved these changes
Dec 2, 2022
codelipenghui
approved these changes
Dec 5, 2022
Contributor
|
/pulsarbot run-failure-checks |
codelipenghui
added
release/2.9.4
type/bug
Contributor
Author
|
/pulsarbot run-failure-checks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
There exists potential non-durable cursor leak problem, if
deleteCursorcalled but without deactive this cursor.Master branch has fix this issue by #17273
Modifications
Deactive cursor in deleteCursor
Documentation
docdoc-requireddoc-not-neededdoc-completeMatching PR in forked repository
gaozhangmin#2