accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-131) ZookeeperInstance gets stuck when given bad host
Date Mon, 15 Oct 2012 17:28:04 GMT


Eric Newton updated ACCUMULO-131:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I applied the patch.  It's better to know about a problem than to just hide it, and not being
able to contact zookeeper for two timeout periods is a problem.
> ZookeeperInstance gets stuck when given bad host
> ------------------------------------------------
>                 Key: ACCUMULO-131
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.1, 1.4.0
>            Reporter: Keith Turner
>            Assignee: Eric Newton
>             Fix For: 1.4.2
>         Attachments: ACCUMULO-131-1.patch
> 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
> Thanks.
> Keith
> {quote}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message