accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4407) Use zk chroot instead of instance id
Date Wed, 17 Aug 2016 22:39:20 GMT


Christopher Tubbs commented on ACCUMULO-4407:

I'm not clear. Are you suggesting just changing our code to chroot to the instance ID, or
are you suggesting changing the layout of the ZK /accumulo area, or both?

It sounds like just the former, but driven by the fact that the layout is confusing.

FWIW, I opened ACCUMULO-1719 awhile back because I found the layout unnecessarily confusing.
That issue is a bit old now, but simplification of the layout could compliment the use of
chroot (it'd certainly be easier to change the layout, without risking breakage, if we were
using chroot).

> Use zk chroot instead of instance id
> ------------------------------------
>                 Key: ACCUMULO-4407
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: core, zookeeper
>            Reporter: Mike Drob
>             Fix For: 2.0.0
> This is something I'd like to see considered for Accumulo 2.0. Probably can't move on
it any sooner because it would break a lot of assumptions, but might be possible to make work
in a backwards compatible way.
> Currently we use instance id in zookeeper to allow for multiple installations sharing
the same zk quorum. This is both a confusing amount of indirection and a headache for operators
when they need to intervene because a uuid is not very human-memory friendly.
> Instead, if we specify a chroot path then we can assume the given accumulo instance is
the only one we will see. This will simplify a lot of APIs because in essence we will be combining
the zk and instance id arguments into one thing.
> I suspect that either we were not aware of zk chroot or it did not exist when we started,
hence not using it. But there's not really any good excuses left today to avoid it.

This message was sent by Atlassian JIRA

View raw message