accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4600) Shell does not fall back to accumulo-site.xml when on classpath
Date Tue, 07 Mar 2017 20:00:39 GMT


Josh Elser commented on ACCUMULO-4600:

bq. I made the (breaking) fix in 1.8.1 as well. Did we miss this issue with the last release
or does it not apply in the 1.8 branch?

I'm guessing it was missed (I don't think I made time to test that out), but I have not yet
confirmed. Steps above should apply..

> Shell does not fall back to accumulo-site.xml when on classpath
> ---------------------------------------------------------------
>                 Key: ACCUMULO-4600
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 1.7.3
>            Reporter: Josh Elser
>            Priority: Critical
> When inspecting 1.7.3-rc1 for the VOTE, I did the following steps:
> * Unpack bin-tarball
> * Copy 3gb native example confs
> * Set {{instance.volumes}} in accumulo-site.xml
> * {{export ACCUMULO_HOME="$(pwd)"}}
> * {{./bin/accumulo init}}
> * {{./bin/}}
> * {{./bin/accumulo shell -u root}}
> The shell failed to connect stating that no tservers were running. By turning on the
debug option to the shell, I could see that the wrong HDFS directory was being used to find
the Accumulo instance ID, {{/accumulo}} instead of {{/accumulo173rc1}}.
> This appears to be because of {{ClientContext#convertClientConfig(Configuration)}} and
 {{Shell#getZooInstance(String, String, ClientConfiguration}}. The client configuration is
empty, therefore, all values end up being pulled from the {{DefaultConfiguration}} instance
instead of the accumulo-site.xml which is on the classpath.

This message was sent by Atlassian JIRA

View raw message