hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8309) TableLockManager: allow lock timeout to be set at the individual lock level
Date Tue, 09 Apr 2013 22:56:17 GMT

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

Ted Yu commented on HBASE-8309:

bq. TableLockManager.java is marked Private. We can change its API.
For Private class, we can change its API / implementation. In this case, the change is to
add a parameter to writeLock().

>From TableLockManager, line 319:
     * @param writeLockTimeoutMs Timeout (in milliseconds) for acquiring a write lock for
     * given table, or -1 for no timeout
How about using -2 for default 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
> 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