[
https://issues.apache.org/jira/browse/ACCUMULO-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900107#comment-15900107
]
Michael Miller commented on ACCUMULO-4600:
------------------------------------------
I think I got burned by this comment:
https://github.com/apache/accumulo/blob/1.7/shell/src/main/java/org/apache/accumulo/shell/ShellOptionsJC.java#L329
What about just making ShellOptionsJC read from accumulo-site like the comment
claims its doing? I'd feel more comfortable modifying ShellOptionsJC instead
of messing with any of the *Configuration or ClientContext objects.
> Shell does not fall back to accumulo-site.xml when on classpath
> ---------------------------------------------------------------
>
> Key: ACCUMULO-4600
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4600
> 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 to
> {{hdfs://localhost:8020/accumulo173rc1}}
> * {{export ACCUMULO_HOME="$(pwd)"}}
> * {{./bin/accumulo init}}
> * {{./bin/start-all.sh}}
> * {{./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
(v6.3.15#6346)
