accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1572) single node zookeeper failure kills connected accumulo servers
Date Mon, 26 Aug 2013 22:26:52 GMT


Keith Turner commented on ACCUMULO-1572:

Its confusing that the ticket is not marked for 1.4.4 since a change was made to 1.4.4 under
this ticket.   The following change was made for 1.5 and 1.6 but not 1.4 under this ticket.
  Its in this change that watchingParent may not be handled properly.  [~ecn] why wasn't the
following change made for 1.4?

@@ -349,6 +349,9 @@ public class ZooLock implements Watcher {
       try { // set the watch on the parent node again
         zooKeeper.getStatus(path, this);
         watchingParent = true;
+      } catch (KeeperException.ConnectionLossException ex) {
+        // we can't look at the lock because we aren't connected, but our session is still
+        log.warn("lost connection to zookeeper");
       } catch (Exception ex) {
         if (lock != null || asyncLock != null) {
> single node zookeeper failure kills connected accumulo servers
> --------------------------------------------------------------
>                 Key: ACCUMULO-1572
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>    Affects Versions: 1.5.0
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Blocker
>             Fix For: 1.4.5, 1.5.1, 1.6.0
> Drew Thornton writes on the user mailing list:
> {quote}
> If one zookeeper node is shutdown/fails/whatever and the rest of the ensemble stays up,
the tablet servers attached as clients to the shutdown node immediately fail. If one of the
clients happens to be the master, the cluster goes down.
> Accumulo does not seem to be failing over to the remaining zookeeper nodes, and this
causes me to restart the individual tablet servers again.
> The zookeeper ensemble is very stable and has plenty of bandwidth/memory/processing,
so taking one node down out of five doesn't crash the zookeepers, just the tablet servers...
> {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