accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1049) Master does not need to get tserver lock
Date Thu, 07 Feb 2013 22:11:12 GMT


Keith Turner commented on ACCUMULO-1049:

I am thinking of making this change for 1.5.  Its an improvement that fixes bugs.

This changes would fix ACCUMULO-1050.

I have some outstanding changes for ACCUMULO-954 which introduce a new state for a ZooLock.
 A state where zoolock is uncertain of the status of the lock in zookeeper.  The master will
have to be modified to handle this new state if it keeps trying to get tserver locks.

This provides a much better solution to ACCUMULO-766.
> Master does not need to get tserver lock
> ----------------------------------------
>                 Key: ACCUMULO-1049
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Assignee: Keith Turner
> 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:

View raw message