accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3779) Shell fails to connect to ZooKeeper when client.conf doesn't exist
Date Thu, 07 May 2015 20:26:00 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533321#comment-14533321
] 

Josh Elser commented on ACCUMULO-3779:
--------------------------------------

Another facet to this I found:

{noformat}
[jelser@cn020 accumulo-copy]$ ./bin/accumulo shell -u root -p secret --debug
2015-05-07 13:23:15,437 [zookeeper.ZooUtil] DEBUG: Trying to read instance id from hdfs://cn020:8020/accumulo/instance_id
2015-05-07 13:24:26,317 [tracer.ZooTraceClient] ERROR: Unabled to get destination tracer hosts
in ZooKeeper, will retry in 5000 milliseconds
java.lang.RuntimeException: Failed to connect to zookeeper (localhost:2181) within 2x zookeeper
timeout period 30000
	at org.apache.accumulo.fate.zookeeper.ZooSession.connect(ZooSession.java:124)
	at org.apache.accumulo.fate.zookeeper.ZooSession.getSession(ZooSession.java:164)
	at org.apache.accumulo.fate.zookeeper.ZooReader.getSession(ZooReader.java:43)
	at org.apache.accumulo.fate.zookeeper.ZooReader.getZooKeeper(ZooReader.java:47)
	at org.apache.accumulo.fate.zookeeper.ZooReader.exists(ZooReader.java:189)
	at org.apache.accumulo.tracer.ZooTraceClient.updateHostsFromZooKeeper(ZooTraceClient.java:120)
	at org.apache.accumulo.tracer.ZooTraceClient$1.run(ZooTraceClient.java:103)
	at org.apache.accumulo.tracer.ZooTraceClient.setInitialTraceHosts(ZooTraceClient.java:116)
	at org.apache.accumulo.tracer.ZooTraceClient.<init>(ZooTraceClient.java:69)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at org.apache.htrace.SpanReceiverBuilder.build(SpanReceiverBuilder.java:115)
	at org.apache.accumulo.core.trace.DistributedTrace.loadSpanReceivers(DistributedTrace.java:161)
	at org.apache.accumulo.core.trace.DistributedTrace.enableTracing(DistributedTrace.java:140)
	at org.apache.accumulo.core.trace.DistributedTrace.enable(DistributedTrace.java:98)
	at org.apache.accumulo.shell.Shell.config(Shell.java:358)
	at org.apache.accumulo.shell.Shell.execute(Shell.java:576)
	at org.apache.accumulo.start.Main$1.run(Main.java:93)
	at java.lang.Thread.run(Thread.java:745)
{noformat}

The tracer might hang because it only observes the client.conf.

> 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
>             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
(v6.3.4#6332)

Mime
View raw message