-
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] [auto-recovery] Improve to the ReplicaitonWorker performance by deleting invalid underreplication nodes #21059
[fix] [auto-recovery] Improve to the ReplicaitonWorker performance by deleting invalid underreplication nodes #21059
Conversation
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.
Please add a test to cover this change
Addressed |
Although ZooKeeper's containerManager exists and automatically deletes empty containers, it is not real-time. If new empty containers arrive while it is working, it cannot delete them promptly. In a user's production environment, the deletion efficiency of the containerManager is lower compared to the efficiency of creating new empty containers. As a result, there will still be many empty containers present. The zookeeper leader logs from the customer, it delete the empty node indeed, but there are still a significant number of empty nodes present.
|
…deleting invalid underreplication nodes (#21059)
Fixes #21058
Main Issue: #21058
Documentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: