[
https://issues.apache.org/jira/browse/HBASE-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590508#comment-13590508
]
Jonathan Hsieh commented on HBASE-7848:
---------------------------------------
[~enis], can you spell out the rules for using the locks in HBASE-7305?
My initial thought was that we take the write lock when we essentially want to
exclusively modify meta (split, move, create, enable/disable), and take the
read lock when you want to prevent other processes from modifying table meta
data (taking snapshot, reading meta whtiout having to worry about it changing
before the next action). It sounds like from conversation yesterday that this
is not correct.
> Use ZK-based read/write lock to make flush-type snapshot robust
> ---------------------------------------------------------------
>
> Key: HBASE-7848
> URL: https://issues.apache.org/jira/browse/HBASE-7848
> Project: HBase
> Issue Type: Improvement
> Components: snapshots
> Affects Versions: 0.96.0
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 7848-v1.txt
>
>
> Current region split following flush would fail snapshot.
> We can utilize ZK-based read/write lock to make flush-type snapshot robust
--
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
