-
Notifications
You must be signed in to change notification settings - Fork 445
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
removes unused zookeeper nodes in upgrade #4712
Conversation
|
||
// clean up nodes no longer in use | ||
zrw.recursiveDelete(zooRoot + ZTRACERS, ZooUtil.NodeMissingPolicy.SKIP); | ||
zrw.recursiveDelete(zooRoot + ZCONF_LEGACY, ZooUtil.NodeMissingPolicy.SKIP); |
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.
@ctubbsii @EdColeman is it ok to remove this zookeeper node in the 3.1 upgrade?
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.
I looked into this a bit and do not think there is anything to actually remove in zookeeper. Looking at ConfigPropertyUpgrader in 2.1 ZCONF_LEGACY is only used for table and namespace config AND the upgrade sets a boolean to remove those.
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.
Going to update this PR to only remove the constant.
For #4587 was reviewing what is outstanding for the elasticity upgrade I noticed these two unused zookeeper constants. Seems they can be removed from ZK if they exist in the 3.1 upgrade. |
No description provided.