hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7546) Obtain a table read lock on region split operations
Date Sat, 23 Feb 2013 01:23:11 GMT

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

stack commented on HBASE-7546:
------------------------------



{code}
+        LOG.warn("Could not release the table lock", ex);
+        //TODO: if we get here, and not abort RS, this lock will never be released
{code}

Abort if we are not already aborting?  Would be reason to adopt curator.

+1 on patch even w/o the above change.

                
> Obtain a table read lock on region split operations
> ---------------------------------------------------
>
>                 Key: HBASE-7546
>                 URL: https://issues.apache.org/jira/browse/HBASE-7546
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>         Attachments: hbase-7546_v1.patch, hbase-7546_v2.patch, hbase-7546_v3.patch
>
>
> As discussed in the parent issue HBASE-7305, we should be coordinating between splits
and table operations to ensure that they don't happen at the same time. In this issue we will
acquire shared read locks for region splits. 

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