accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1049) Master does not need to get tserver lock
Date Sat, 09 Feb 2013 00:03:12 GMT

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

Hudson commented on ACCUMULO-1049:
----------------------------------

Integrated in Accumulo-Trunk-Hadoop-2.0 #76 (See [https://builds.apache.org/job/Accumulo-Trunk-Hadoop-2.0/76/])
    ACCUMULO-1049 modified master to stop locking tserver nodes and just monitor  tserver
nodes in zookeeper (Revision 1444259)

     Result = FAILURE
kturner : 
Files : 
* /accumulo/trunk/server/src/main/java/org/apache/accumulo/server/master/LiveTServerSet.java

                
> Master does not need to get tserver lock
> ----------------------------------------
>
>                 Key: ACCUMULO-1049
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1049
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.5.0, 1.4.3
>
>
> Every tserver has a lock in zookeeper.  The master tries to get this lock and when it
does it assumes the tserver is dead.  It seems like this may no longer be necessary since
changes made in 1.3.  The master used to only keep track of ip and port to identify a tablet
server.  It needed to know when it got the lock to detect the difference between two tablet
server instances at the same ip and port.
> Since 1.3 the master keeps distinctive info about a tablet server now and can detect
the difference between tablet server instances.  Making the master just monitor the current
tablet server locks instead of trying to get the lock would simplify the master code.  

--
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