Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 14 Apr 2013 03:40:17 +0000 (UTC)
From: "Jerry He (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12641727.1365543748870.164376.1365910817486@arcas>
In-Reply-To: <JIRA.12641727.1365543748870@arcas>
References: <JIRA.12641727.1365543748870@arcas>
Subject: [jira] [Updated] (HBASE-8309) TableLockManager: allow lock timeout
 to be set at the individual lock level
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry He updated HBASE-8309:
----------------------------

    Attachment: HBASE-8309-v3.patch
    
> TableLockManager: allow lock timeout to be set at the individual lock level
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-8309
>                 URL: https://issues.apache.org/jira/browse/HBASE-8309
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.95.0
>            Reporter: Jerry He
>            Assignee: Jerry He
>            Priority: Minor
>             Fix For: 0.98.0, 0.95.1, 0.95.2
>
>         Attachments: HBASE-8309.patch, HBASE-8309-v2.patch, HBASE-8309-v3.patch
>
>
> Currently the lock timeout values and defaults are set and shared at the TableLockManager level.
> One TableLockManager is shared on the master. We should allow the lock timeout to be set at individual lock level when we instantiate the lock. Components using the locks may have different timeout preferences. 

--
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