-
Notifications
You must be signed in to change notification settings - Fork 3.8k
[fix][metadata] Re-register the bookie after a metadata session loss #26713
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
Open
dao-jun
wants to merge
5
commits into
apache:master
Choose a base branch
from
dao-jun:pr-p2-registration-selfheal
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,122
−82
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
778f2c2
[fix][metadata] Re-register the bookie after a metadata session loss
dao-jun 00569e8
[fix][metadata] Test the bookie registration revalidation loop
dao-jun 5a17860
[fix][metadata] Complete the resource lock adoption and release paths
dao-jun 17b3bf6
[fix][metadata] Carry the bookie registration recovery in the lock layer
dao-jun 19e42c6
[fix][metadata] Keep the revalidation entry point private
dao-jun File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
354 changes: 304 additions & 50 deletions
354
...tadata/src/main/java/org/apache/pulsar/metadata/bookkeeper/PulsarRegistrationManager.java
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Potential deadlock on the ZooKeeper path. For example:
old.release(), sendsstore.delete(), and is descheduled before attaching its.thenRuncompletion. It still holds the old lock monitor.LockManagerImplmonitor and blocks here inreplaced.retire()waiting for A..thenRunruns inline on A. ItsexpiredFuture.complete()invokes the manager cleanup callback, which waits for the manager monitor held by the create callback.Both threads are now blocked. ZooKeeper's single event executor does not prevent this because A's late completion runs on A's thread. Avoid taking the old lock monitor while holding the manager monitor, and preserve the map replacement ordering.