Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 27 Jul 2012 05:35:36 +0000 (UTC)
From: "Alex Feinberg (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <577214053.109478.1343367336308.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <626066645.55514.1336760449609.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5991) Introduce sequential ZNode based
 read/write locks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alex Feinberg commented on HBASE-5991:
--------------------------------------

Got tests for write lock passing (verifying that write locks excludes other writers). Now writing test for read locks (verifying that write locks exclude readers, but that readers do not exclude other reads). 

After that the tasks are to integrate misc functionality (printing information on lock owners) into the code, clean up, and then replace DistributedLock with WriteLock and run full end-to-end tests. Will put up a diff once this is done. 

                
> Introduce sequential ZNode based read/write locks 
> --------------------------------------------------
>
>                 Key: HBASE-5991
>                 URL: https://issues.apache.org/jira/browse/HBASE-5991
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Alex Feinberg
>            Assignee: Alex Feinberg
>
> This is a continuation of HBASE-5494:
> Currently table-level write locks have been implemented using non-sequential ZNodes as part of HBASE-5494 and committed to 89-fb branch. This issue is to track converting the table-level locks to sequential ZNodes and supporting read-write locks, as to solve the issue of preventing schema changes during region splits or merges.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira