[
https://issues.apache.org/jira/browse/ACCUMULO-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559647#comment-14559647
]
Josh Elser commented on ACCUMULO-3779:
--------------------------------------
[~jcnowell], thanks for asking.
bq. the relationship is unclear (one is deprecating the other for some set of
use cases?)
accumulo-site.xml is meant for "server-side" while client.conf is meant for
"client-side". This is a push towards ensuring a strong delineation between
what configuration is present for clients to use and what configuration is
present for servers. We can go into this at more length elsewhere.
bq. INI style key/value pairs equivalent to accumulo-site.xml
It's a [Java properties file|http://en.wikipedia.org/wiki/.properties]. It's a
subset of what is present in accumulo-site.xml. The full list of properties are
in
[ClientProperties|https://github.com/apache/accumulo/blob/68b8cd7c9169c1d2e8eabfb84c9d977c8acc8973/core/src/main/java/org/apache/accumulo/core/client/ClientConfiguration.java#L54].
bq. I can find neither documentation nor an example for client.conf
bq. Should I (probably with guidance) make a new Issue for this?
Yes, please do. This documentation should've been written when it was
introduced in 1.6.0, but it seems like it wasn't. Client-side configuration has
been a bit of a moving window throughout 1.6, but I'm convinced that it's the
direction we want to move.
The most trivial client.conf file you can make is likely:
{code}
instance.zookeeper.host=localhost:2181
{code}
> 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)
