[
https://issues.apache.org/jira/browse/HBASE-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421057#comment-13421057
]
Jesse Yates commented on HBASE-5991:
------------------------------------
@Alex not to press too much, but any progress? Over on HBASE-6055 it would be
really nice to not just have locks on master operations, but full-fledged table
metadata and/or read/write locks. That way an operation that spans
regionservers could lock a table (checkable at the regionserver as well),
preventing things like:
* splits
* merges
* region reassignment
Also, it would be nice if the lock would be flexible enough to be used to lock
a table down to a read-only state (so any writes get blocked/regjected until
the table is unlocked). I think something along the lines of what was up in
HBASE-5494 would be the right way to go (leased based lock control and watcher
in ZK), perhaps with the addition of some lock listeners.
If you are busy with other stuff, I'd be glad to work on it.
> Introduce sequential ZNode based read/write locks
> --------------------------------------------------
>
> Key: HBASE-5991
> URL: https://issues.apache.org/jira/browse/HBASE-5991
> Project: HBase
> Issue Type: Improvement
> Reporter: Alex Feinberg
> Assignee: Alex Feinberg
>
> This is a continuation of HBASE-5494:
> Currently table-level write locks have been implemented using non-sequential
> ZNodes as part of HBASE-5494 and committed to 89-fb branch. This issue is to
> track converting the table-level locks to sequential ZNodes and supporting
> read-write locks, as to solve the issue of preventing schema changes during
> region splits or merges.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
