hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8309) TableLockManager: allow lock timeout to be set at the individual lock level
Date Tue, 24 Dec 2013 23:33:50 GMT

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

Hadoop QA commented on HBASE-8309:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .
  ATTACHMENT ID: 12578634

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8281//console

This message is automatically generated.

> 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
>            Reporter: Jerry He
>            Assignee: Jerry He
>            Priority: Minor
>             Fix For: 0.99.0
>         Attachments: HBASE-8309-v2.patch, HBASE-8309-v3.patch, HBASE-8309.patch
> Currently the lock timeout values and defaults are set and shared at the TableLockManager
> 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 was sent by Atlassian JIRA

View raw message