accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel P Truitt (JIRA)" <>
Subject [jira] [Created] (ACCUMULO-1277) Race condition between master and tserver when acquiring tserver lock
Date Mon, 15 Apr 2013 21:52:16 GMT
Daniel P Truitt created ACCUMULO-1277:

             Summary: Race condition between master and tserver when acquiring tserver lock
                 Key: ACCUMULO-1277
             Project: Accumulo
          Issue Type: Bug
          Components: master, tserver
    Affects Versions: 1.4.3, 1.5.0
            Reporter: Daniel P Truitt
            Assignee: Eric Newton

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.checkServer(Set<TServerInstance>, Set<TServerInstance>, 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

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