[
https://issues.apache.org/jira/browse/HBASE-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590997#comment-13590997
]
Jonathan Hsieh commented on HBASE-7965:
---------------------------------------
As much as I like the locking mechanisms, I'm concerned about backporting them
to a stable release. Some questions I have in mind are:
# Adding locks prevents races, but could enable deadlocks. We've lived with
these races for a long time (at least since 0.90) and basically understand
them. This is a fundamentally different failure scenario and has me worried.
# This is going to affect a vital path (can't use hbase if you can't create
tables). I'd honestly like some evidence (a story!) about some long running
tests with fault injection using this mechanism. This will go a long way to
allaying my concerns.
# What is the rolling upgrade story (0.94.5 -> 0.94.7). Does cause any
incompatibilities?
> Port table locking to 0.94 (HBASE-7305, HBASE-7546, HBASE-7933)
> ---------------------------------------------------------------
>
> Key: HBASE-7965
> URL: https://issues.apache.org/jira/browse/HBASE-7965
> Project: HBase
> Issue Type: New Feature
> Components: master, Zookeeper
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.94.7
>
>
> Port table locking to 0.94 (HBASE-7305, HBASE-7546, HBASE-7933). This is a
> new feature, but there has been some interest, and it is necessary for
> snapshots, and online merge, which are also candidates for backport.
> If we port snapshots, we might need HBASE-7848 as well.
> We can also do disabled by default.
--
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
