hbase-issues mailing list archives

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

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

Enis Soztutar commented on HBASE-7546:
--------------------------------------

Ted, I thought https://issues.apache.org/jira/secure/attachment/12574427/HBaseTableLocks_v2.pdf
addressed your comments. From section Read Lock vs Write Lock:
{quote}
Read lock means that it is a shared lock, while write lock is an exclusive lock. We want region
splits to acquire a read lock on the table, since we want concurrent splits happening at the
same time. Remember only read lock is shared, write lock is exclusive. So for operations that
we want to happen concurrently (like region splits) we want to acquire a read lock.
{quote}
                
> 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, hbase-7546_v5.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