accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ACCUMULO-1277) Race condition between master and tserver when acquiring tserver lock
Date Tue, 17 Sep 2013 20:09:51 GMT

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

Keith Turner edited comment on ACCUMULO-1277 at 9/17/13 8:08 PM:
-----------------------------------------------------------------

The following stack trace may indicate the occurrence of this bug in your Accumulo 1.4.3 cluster
when attempting to start tablet servers:

{noformat}
Uncaught exception in TabletServer.main, exiting
         java.lang.RuntimeException: java.lang.RuntimeException: Too many retries, exiting.
                 at org.apache.accumulo.server.tabletserver.TabletServer.announceExistence(TabletServer.java:2684)
                 at org.apache.accumulo.server.tabletserver.TabletServer.run(TabletServer.java:2703)
                 at org.apache.accumulo.server.tabletserver.TabletServer.main(TabletServer.java:3168)
                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                 at java.lang.reflect.Method.invoke(Method.java:597)
                 at org.apache.accumulo.start.Main$1.run(Main.java:89)
                 at java.lang.Thread.run(Thread.java:662)
         Caused by: java.lang.RuntimeException: Too many retries, exiting.
                 at org.apache.accumulo.server.tabletserver.TabletServer.announceExistence(TabletServer.java:2681)
                 ... 8 more
{noformat}
                
      was (Author: charlescva):
    The following stack trace may indicate the occurrence of this bug in your Accumulo 1.4.3
cluster when attempting to start tablet servers:

Uncaught exception in TabletServer.main, exiting
         java.lang.RuntimeException: java.lang.RuntimeException: Too many retries, exiting.
                 at org.apache.accumulo.server.tabletserver.TabletServer.announceExistence(TabletServer.java:2684)
                 at org.apache.accumulo.server.tabletserver.TabletServer.run(TabletServer.java:2703)
                 at org.apache.accumulo.server.tabletserver.TabletServer.main(TabletServer.java:3168)
                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                 at java.lang.reflect.Method.invoke(Method.java:597)
                 at org.apache.accumulo.start.Main$1.run(Main.java:89)
                 at java.lang.Thread.run(Thread.java:662)
         Caused by: java.lang.RuntimeException: Too many retries, exiting.
                 at org.apache.accumulo.server.tabletserver.TabletServer.announceExistence(TabletServer.java:2681)
                 ... 8 more

                  
> Race condition between master and tserver when acquiring tserver lock
> ---------------------------------------------------------------------
>
>                 Key: ACCUMULO-1277
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1277
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>    Affects Versions: 1.4.3
>            Reporter: Daniel P Truitt
>            Assignee: Keith Turner
>             Fix For: 1.4.4, 1.5.0
>
>
> When restarting a stopped tserver, the following happens:
> The tserver (in TabletServer.announceExistence()) creates an entry in zookeeper at /accumulo/instance-id/tserver/host:port.
> This in turn triggers master to execute the call chain:
> LiveTServerSet.process(WatchedEvent)
> LiveTServerSet.scanServers()
> LiveTServerSet.checkServer(Set<TServerInstance>, Set<TServerInstance>, String,
String)
> The checkServer() method checks to see if the ZooLock data has been created yet (if tserver
loses the race, it has not yet been created) causing master to then delete the tserver node.
 
> When the tserver attempts to create the ZooLock, the parent path no longer exists and
creating the lock fails.  Eventually the tserver will time out waiting to create the lock,
and fail to start.
> This problem is easier to reproduce in a smallish cluster using a single zookeeper node,
where there is more latency between the tserver and zookeeper than there is between the master
and zookeeper.
> This behavior was introduced in the fix for ACCUMULO-1049.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message