You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2014/12/01 05:19:13 UTC

[jira] [Commented] (HBASE-12577) Disable distributed log replay by default

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

Enis Soztutar commented on HBASE-12577:
---------------------------------------

We have never turned it on for 0.98. 0.99.0 and 0.99.1 shipped with it being on, but they are non-production releases. HBASE-10888 is the first attempt to turn it on by default AFAIK. 




> Disable distributed log replay by default
> -----------------------------------------
>
>                 Key: HBASE-12577
>                 URL: https://issues.apache.org/jira/browse/HBASE-12577
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Jeffrey Zhong
>            Priority: Critical
>             Fix For: 0.99.2
>
>         Attachments: HBASE-12567.patch, HBASE-12567.patch
>
>
> Distributed log replay is an awesome feature, but due of HBASE-11094, the rolling upgrade story from 0.98 is hard to explain / enforce. 
> The fix for HBASE-11094 only went into 0.98.4, meaning rolling upgrades from 0.98.4- might lose data during the upgrade. 
> I feel no matter how much documentation / warning we do, we cannot prevent users from doing rolling upgrades from 0.98.4- to 1.0. And we do not want to inconvenience the user by requiring a two step rolling upgrade.  
> Thus I think we should disable dist log replay for 1.0, and re-enable it again for 1.1 (if rolling upgrade from 0.98 is not supported). 
> ie. undo: HBASE-10888



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)