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-8309) TableLockManager: allow lock timeout to be set at the individual lock level
Date Wed, 10 Apr 2013 01:25:14 GMT

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

Enis Soztutar commented on HBASE-8309:

Is there really a solid use case for this? Underlying zk based lock implementation provides
timeout support at a more granular level, but I've opted out in the TableLockManager level.
Why would you obtain a lock with a different timeout? 
> 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
> 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 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