Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 26 Mar 2013 05:01:16 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12634946.1362186850353.53855.1364274076276@arcas>
In-Reply-To: <JIRA.12634946.1362186850353@arcas>
References: <JIRA.12634946.1362186850353@arcas>
Subject: [jira] [Commented] (HBASE-7977) Online merge should acquire table
 lock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-7977:
------------------------------

[~enis] Oh, I was just thinking of the case of a stuck lock (brought on by review of your table).  A little lock symbol showing beside table name in a table listing would be kinda cool and might be useful in case where operator is trying to figure why an operation is not working (UI would stale lock that has been in place N hours).  No biggie.  No hurry Enis.
                
> 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