accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Resolved] (ACCUMULO-4600) Shell does not fall back to accumulo-site.xml when on classpath
Date Fri, 10 Mar 2017 01:13:38 GMT


Christopher Tubbs resolved ACCUMULO-4600.
    Resolution: Fixed
      Assignee: Michael Miller

Looks like this was pushed to 1.7 branch by Mike. I've merged it forward, assigned this issue
to him, and closed it. If this isn't done, please reopen.

> Shell does not fall back to accumulo-site.xml when on classpath
> ---------------------------------------------------------------
>                 Key: ACCUMULO-4600
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>            Reporter: Josh Elser
>            Assignee: Michael Miller
>            Priority: Blocker
>             Fix For: 1.7.3, 1.8.2, 2.0.0
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
> 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/}}
> * {{./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