[
https://issues.apache.org/jira/browse/HBASE-7305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584100#comment-13584100
]
ramkrishna.s.vasudevan commented on HBASE-7305:
-----------------------------------------------
Going thro the patch, currenlty we have use case only with WriteLock?
So when we do region assignments thro balancing then we should create a
readlock on the path /znode/table-lock for the given table.
Now when this process is going on we will stop the user from Disabling or
Modifying the table. Am i right?
That part is yet to be implemented?
> ZK based Read/Write locks for table operations
> ----------------------------------------------
>
> Key: HBASE-7305
> URL: https://issues.apache.org/jira/browse/HBASE-7305
> Project: HBase
> Issue Type: Bug
> Components: Client, master, Zookeeper
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.96.0
>
> Attachments: 7305-v11.txt, hbase-7305_v0.patch, hbase-7305_v10.patch,
> hbase-7305_v13.patch, hbase-7305_v14.patch, hbase-7305_v15.patch,
> hbase-7305_v1-based-on-curator.patch, hbase-7305_v2.patch,
> hbase-7305_v4.patch, hbase-7305_v9.patch
>
>
> This has started as forward porting of HBASE-5494 and HBASE-5991 from the
> 89-fb branch to trunk, but diverged enough to have it's own issue.
> The idea is to implement a zk based read/write lock per table. Master
> initiated operations should get the write lock, and region operations (region
> split, moving, balance?, etc) acquire a shared read lock.
--
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
