hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7965) Port table locking to 0.94 (HBASE-7305, HBASE-7546, HBASE-7933)
Date Sat, 02 Mar 2013 03:05:14 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591242#comment-13591242
] 

Enis Soztutar commented on HBASE-7965:
--------------------------------------

bq. If we cannot convince Jon and Elliot sufficiently that this backport does not destabilize
0.94 that we should not do it. So what can we do to create confidence in this backport?
Jon, Elliot, please see my notes at https://issues.apache.org/jira/secure/attachment/12571721/HBaseTableLocks.pdf.
I propose to port as disabled by default. In which case NullTableLockManager will be the TLM
implementation doing no-ops. The implementation does not touch critical paths. 
                
> 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

Mime
View raw message