[
https://issues.apache.org/jira/browse/HBASE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-11296.
------------------------------------
Resolution: Invalid
We don't need a new JIRA for a task that should be part of another (that will
probably be resolved as Wont Fix)
> TableLockManager should provide API which returns whether specific table has
> outstanding lock
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-11296
> URL: https://issues.apache.org/jira/browse/HBASE-11296
> Project: HBase
> Issue Type: Task
> Reporter: Ted Yu
>
> In HBASE-11282, one proposal is to skip region movement during the period
> when table lock is held on the underlying table.
> Currently TableLockManager provides the following API which iterates through
> all locks:
> {code}
> public void visitAllLocks(MetadataHandler handler) throws IOException {
> {code}
> The above API is heavyweight for this use case where table name is known.
> This JIRA is to add new API which returns whether given table has outstanding
> read / write lock.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
