[
https://issues.apache.org/jira/browse/ACCUMULO-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559628#comment-14559628
]
James Nowell commented on ACCUMULO-3779:
----------------------------------------
The WARN level log message in ClientConfiguration added by this commit alerted
me that I'm currently not using this file, but I can find neither documentation
nor an example for client.conf. I gather that client.conf and accumulo-site.xml
are related in some fashion, but the relationship is unclear (one is
deprecating the other for some set of use cases?).
Forgive me if this is the wrong place to ask (created a Jira account to ask
about this), but what am I supposed to put in this file? INI style key/value
pairs equivalent to accumulo-site.xml? A subset of those values required for a
client to make a successful connection? Should I (probably with guidance) make
a new Issue for this?
> Shell fails to connect to ZooKeeper when client.conf doesn't exist
> ------------------------------------------------------------------
>
> Key: ACCUMULO-3779
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3779
> Project: Accumulo
> Issue Type: Bug
> Components: shell
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Blocker
> Labels: 1.7.0_QA
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Stood up 1.7.0, forgot to make a client.conf (there wasn't a template
> included in the example confs).
> Tried to connect to the shell and it just timed out trying to talk to
> ZooKeeper at the default host of "localhost:2181". I feel like this is a
> regression against 1.6 because things used to attempt to work by trying to
> read accumulo-site.xml.
> If we are intentionally not supporting automatic fallback to
> accumulo-site.xml, we should have a log message that informs the user when we
> construct a ClientConfiguration without any actual configuration (as that's
> likely an error).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
