hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7546) Obtain a table read lock on region split operations
Date Sat, 02 Mar 2013 00:51:13 GMT

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

Ted Yu commented on HBASE-7546:
-------------------------------

Table split modifies table metadata. I tend to think that a write lock is more appropriate
in this scenario.

Table snapshot, on the other hand, doesn't change table metadata. A read lock would fit.

This way, we achieve mutual exclusion between the two operations.
                
> 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
>             Fix For: 0.95.0
>
>         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