You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Eric Newton (Assigned) (JIRA)" <ji...@apache.org> on 2011/11/30 19:59:40 UTC
[jira] [Assigned] (ACCUMULO-131) ZookeeperInstance gets stuck when
given bad host
[ https://issues.apache.org/jira/browse/ACCUMULO-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Newton reassigned ACCUMULO-131:
------------------------------------
Assignee: Eric Newton
> ZookeeperInstance gets stuck when given bad host
> ------------------------------------------------
>
> Key: ACCUMULO-131
> URL: https://issues.apache.org/jira/browse/ACCUMULO-131
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Reporter: Keith Turner
> Assignee: Eric Newton
>
> Keith Massey reported the following issue on the mailing list.
> {quote}
> A user of our recently filed a bug with us because our code hung forever when she gave us an address for a zookeeper that was not running. I think I've traced the problem into org.apache.accumulo.core.zookeeper.ZooSession.connect(). If the connection to the zookeeper fails it throws a ConnectException, which gets caught by the catch (IOException) block, which logs the message and keeps trying infinitely. It's definitely user error passing in an invalid zookeeper. But shouldn't that method bail out after some time?
> Thanks.
> Keith
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira