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-7977) Online merge should acquire table lock
Date Tue, 26 Mar 2013 03:13:17 GMT

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

Enis Soztutar commented on HBASE-7977:

I think J-M made that comment before the discussions in HBASE-7546, and design doc at HBASE-7305.
We are acquiring a read lock on the table, I don't think lock being expensive is relevant
(because it is not). Correct me if I'm wrong J-M. 
bq. We need to figure a way of showing locks in UI?
Do you have anything specific in mind. Locks come and go during the splits and master operations.
Should we do smt like task statuses? 
> Online merge should acquire table lock
> --------------------------------------
>                 Key: HBASE-7977
>                 URL: https://issues.apache.org/jira/browse/HBASE-7977
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, Region Assignment, regionserver
>    Affects Versions: 0.95.0, 0.98.0
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.95.0, 0.98.0
>         Attachments: hbase-7977_v1.patch
> Once online merge (HBASE-7403) is in, we should ensure that we acquire a table write
lock during the merge. 

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

View raw message