[ACCUMULO-3779] Shell fails to connect to ZooKeeper when client.conf doesn't exist

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.6.3, 1.7.0
• Component/s: shell
• Labels: 1.7.0_QA
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 07/May/15 04:34
• Updated: 01/Nov/16 20:26
• Resolved: 07/May/15 21:07

Description

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).

Issue Links

• breaks: ACCUMULO-4505 Shell still reads accumulo-site.xml when using Zookeeper CLI options
• is broken by: ACCUMULO-3465 ClientOpts doesn't use zk and instance properties from client config file