Skip to content
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

Merged
merged 3 commits into from
Jul 22, 2024

Conversation

keith-turner
Copy link
Contributor

No description provided.


// clean up nodes no longer in use
zrw.recursiveDelete(zooRoot + ZTRACERS, ZooUtil.NodeMissingPolicy.SKIP);
zrw.recursiveDelete(zooRoot + ZCONF_LEGACY, ZooUtil.NodeMissingPolicy.SKIP);
Copy link
Contributor Author

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?

Copy link
Contributor Author

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.

Copy link
Contributor Author

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.

@keith-turner
Copy link
Contributor Author

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.

@keith-turner keith-turner linked an issue Jun 27, 2024 that may be closed by this pull request
@ctubbsii ctubbsii added this to the 3.1.0 milestone Jul 12, 2024
@keith-turner keith-turner merged commit 97f2f62 into apache:main Jul 22, 2024
8 checks passed
@keith-turner keith-turner deleted the upgrade_review_31 branch July 22, 2024 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement upgrade from 3.1 to 4.0
3 participants