Return-Path: 
 <notifications-return-5305-apmail-accumulo-notifications-archive=accumulo.apache.org@accumulo.apache.org>
X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org
Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 93125104CA
	for <apmail-accumulo-notifications-archive@minotaur.apache.org>;
 Wed, 17 Apr 2013 00:21:16 +0000 (UTC)
Received: (qmail 3796 invoked by uid 500); 17 Apr 2013 00:21:16 -0000
Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org
Received: (qmail 3765 invoked by uid 500); 17 Apr 2013 00:21:16 -0000
Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@accumulo.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@accumulo.apache.org>
List-Post: <mailto:notifications@accumulo.apache.org>
List-Id: <notifications.accumulo.apache.org>
Reply-To: jira@apache.org
Delivered-To: mailing list notifications@accumulo.apache.org
Received: (qmail 3756 invoked by uid 99); 17 Apr 2013 00:21:16 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2013 00:21:16 +0000
Date: Wed, 17 Apr 2013 00:21:16 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12642619.1366062714432.177550.1366158076451@arcas>
In-Reply-To: <JIRA.12642619.1366062714432@arcas>
References: <JIRA.12642619.1366062714432@arcas>
Subject: [jira] [Commented] (ACCUMULO-1277) Race condition between master
 and tserver when acquiring tserver lock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Hudson commented on ACCUMULO-1277:
----------------------------------

Integrated in Accumulo-1.4.x #293 (See [https://builds.apache.org/job/Accumulo-1.4.x/293/])
    ACCUMULO-1277 made master delay deleting lockless tserver nodes in zookeeper (Revision 1468589)

     Result = SUCCESS
kturner : 
Files : 
* /accumulo/branches/1.4
* /accumulo/branches/1.4/src
* /accumulo/branches/1.4/src/core
* /accumulo/branches/1.4/src/server
* /accumulo/branches/1.4/src/server/src
* /accumulo/branches/1.4/src/server/src/main/java/org/apache/accumulo/server/master/LiveTServerSet.java
* /accumulo/branches/1.4/src/server/src/main/java/org/apache/accumulo/server/zookeeper/ZooLock.java

                
> 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.5.0, 1.4.4
>
>
> 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