hbase-issues mailing list archives

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

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

Andrew Purtell updated HBASE-8309:
----------------------------------

    Affects Version/s:     (was: 0.95.0)
        Fix Version/s:     (was: 0.98.0)
                       0.99.0

> 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
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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message