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 18:09:15 GMT

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

Enis Soztutar commented on HBASE-7977:

bq. Just one question. If the cluster is brought down while one operation with a lock is in
progress, what will be the behaviour when the cluster will be restarted?
All the lock znodes are EPHEMERAL. They will be gone if the process (RS or master) who acquired
the lock closes its zk session. 
bq. What will be the options for the operators to clean that? They can only go to ZK and clear
the node?
Going to zk to clean would be the easiest way. Maybe we can add that to hbck. 
> 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