accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3779) Shell fails to connect to ZooKeeper when client.conf doesn't exist
Date Thu, 07 May 2015 17:41:00 GMT


Christopher Tubbs commented on ACCUMULO-3779:

A warning when no client.conf is found seems reasonable, as does adding a template for it.
I wonder if the template should be named "client.conf.template", though, so it's not automatically
used (could interfere with existing deployments if a user has one in a lower-priority location)?

I don't remember completely dropping support for fallback to using accumulo-site.xml, but
I would be in favor of that, especially if we made it easier to create/use client.conf and
warned appropriately.

> Shell fails to connect to ZooKeeper when client.conf doesn't exist
> ------------------------------------------------------------------
>                 Key: ACCUMULO-3779
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.7.0
> 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

View raw message