[
https://issues.apache.org/jira/browse/HBASE-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608518#comment-13608518
]
Enis Soztutar commented on HBASE-7848:
--------------------------------------
In all other handlers, the contract is that if prepare() throws an exception,
we can assume that the table lock is not held. Prepare is responsible for
catching the exception, and releasing the lock (see
CreateTableHandler.prepare()). Unfortunately there is no single super class for
all the handlers to document this, so I lefts some comments on table lock
acquire(). Other than that, I don't know how we can better document this.
Suggestions welcome.
> Use ZK-based read/write lock to make flush-type snapshot robust against table
> enable/disable/alter
> --------------------------------------------------------------------------------------------------
>
> 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, 7848-v2.txt, hbase-7848_v2.patch
>
>
> 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
