-
Notifications
You must be signed in to change notification settings - Fork 455
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
Use ZooKeeper with a base directory ("chroot") instead of always specifying full path #4809
Milestone
Comments
I can look into this. |
This was referenced Dec 14, 2024
meatballspaghetti
added a commit
to meatballspaghetti/accumulo
that referenced
this issue
Jan 28, 2025
- Delete ClientContext.getZooKeeperRoot() - Remove uses of ZooUtil.getRoot() in which Chroot would apply - Inline TabletsMetadata.getRootMetadata() - Remove AdminTest.testZooKeeperTserverPath() - Remove other functionality whose purpose revolved around the root path which will be Chroot-ed. Resolves: apache#4809
meatballspaghetti
added a commit
to meatballspaghetti/accumulo
that referenced
this issue
Jan 30, 2025
- Fix misc errors and refactors from previous ZooKeeper Chroot path changes - Add expect line to PropStoreEventTest temporarily Resolves: apache#4809
meatballspaghetti
added a commit
to meatballspaghetti/accumulo
that referenced
this issue
Feb 6, 2025
- Delete ClientContext.getZooKeeperRoot() - Remove uses of ZooUtil.getRoot() in which Chroot would apply - Inline TabletsMetadata.getRootMetadata() - Remove AdminTest.testZooKeeperTserverPath() - Remove other functionality whose purpose revolved around the root path which will be Chroot-ed. Resolves: apache#4809
meatballspaghetti
added a commit
to meatballspaghetti/accumulo
that referenced
this issue
Feb 6, 2025
- Fix misc errors and refactors from previous ZooKeeper Chroot path changes - Add expect line to PropStoreEventTest temporarily Resolves: apache#4809
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was originally described at https://issues.apache.org/jira/browse/ACCUMULO-4407
We pass around the instanceId a lot in Accumulo, and the vast majority of the time, it's just so we can pass it as part of the path to a ZooKeeper object that is already constructed. We can avoid a lot of this, and simplify the code quite a bit if we just construct the ZooKeeper object using the instanceId as part of the connection string, so all absolute paths are then relative to the instanceId directory, similar to one might do with
chroot
.Here's an example of what the code change would look like:
We still need to connect without the instanceId when we look up the instanceId from the instance name (which is needed on the client side), but in all other cases, we don't need it.
The text was updated successfully, but these errors were encountered: