accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3540) Allow settting instance_volumes and instance_volumes_replacements via zk
Date Wed, 28 Jan 2015 19:35:36 GMT


Christopher Tubbs commented on ACCUMULO-3540:

Because the semantics of the {{instance.}} prefix is such that it must be the same across
the entire cluster, we'd have to consider introducing a new property ({{general.volumes}}?)
to do this. Because of the churn with the introduction of volumes in 1.6, and the additional
work outlined in ACCUMULO-3535, I'd like to postpone consideration of adding a new property
until we get rid of {{instance.dfs.dir}} and {{instance.dfs.uri}}, which we can do in 2.0.
If there's another solution, which doesn't involve creating a new property, that could work
sooner, though.

> Allow settting instance_volumes and instance_volumes_replacements via zk
> ------------------------------------------------------------------------
>                 Key: ACCUMULO-3540
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: John Vines
> Currently these settings are under the catch-all of no instance keys allowed in zk. Unfortunately,
I feel that's a bit far reaching as these two settings, I feel, don't need to be accumulo-site.xml
only. These spaces shouldn't be used until after we get ZK information. Furthermore, now that
we support multiple filesystems, our current implementation does not allow us to dynamically
add more filesystems, so that would be another benefit.

This message was sent by Atlassian JIRA

View raw message