-
Notifications
You must be signed in to change notification settings - Fork 12
Do not delete zero-copy locks by default #391
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
kirillgarbar
wants to merge
1
commit into
yandex:main
Choose a base branch
from
kirillgarbar:delete-zk-locks-option
base: main
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.
Open
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
Contributor
Reviewer's GuideThis PR refactors two Zookeeper-related CLI commands to make zero-copy lock deletion opt-in by adding a new flag and guarding the existing deletion logic with it. Sequence diagram for guarded zero-copy lock deletion in clickhouse_hosts_commandsequenceDiagram
actor User
participant CLI
participant "delete_zero_copy_locks()"
User->>CLI: Run clickhouse_hosts_command with/without --delete-zero-copy-locks
CLI->>CLI: Check if delete_locks flag is set
alt delete_locks is True
CLI->>"delete_zero_copy_locks()": Delete locks for each host
else delete_locks is False
CLI->>CLI: Skip zero-copy lock deletion
end
Sequence diagram for guarded zero-copy lock deletion in remove_hosts_from_tablesequenceDiagram
actor User
participant CLI
participant "delete_zero_copy_locks()"
User->>CLI: Run remove_hosts_from_table with/without --delete-zero-copy-locks
CLI->>CLI: Check if delete_locks flag is set
alt delete_locks is True
CLI->>"delete_zero_copy_locks()": Delete locks for each host
else delete_locks is False
CLI->>CLI: Skip zero-copy lock deletion
end
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary by Sourcery
Make zero-copy lock deletion opt-in by adding a flag and conditionally running the cleanup only when requested
Enhancements: