[
https://issues.apache.org/jira/browse/HBASE-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031147#comment-14031147
]
Jeffrey Zhong commented on HBASE-11094:
---------------------------------------
{quote}
What does the above mean Jeffrey Zhong?
{quote}
I'll leave distributedLogReplay on by default in master branch. Since we can't
rolling upgrade from pre 0.98.4 version to 1.0, I'll create a JIRA to see if we
need to turn it off by default to support rolling upgrade to 1.0.
{qutoe}
Can you add a release note saying what has been implemented?
{quote}
Done.
{quote}
To be clear, mode is LOG_REPLAY currently in master?
{quote}
Yes.
Thanks for looking at this again.
> Distributed log replay is incompatible for rolling restarts
> -----------------------------------------------------------
>
> Key: HBASE-11094
> URL: https://issues.apache.org/jira/browse/HBASE-11094
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Jeffrey Zhong
> Priority: Blocker
> Fix For: 0.99.0
>
> Attachments: hbase-11094-v2.patch, hbase-11094-v3.patch,
> hbase-11094-v4.patch, hbase-11094-v5.1.patch, hbase-11094-v5.patch,
> hbase-11094.patch
>
>
> 0.99.0 comes with dist log replay by default (HBASE-10888). However, reading
> the code and discussing this with Jeffrey, we realized that the dist log
> replay code is not compatible with rolling upgrades from 0.98.0 and 1.0.0.
> The issue is that, the region server looks at it own configuration to decide
> whether the region should be opened in replay mode or not. The open region
> RPC does not contain that info. So if dist log replay is enabled on master,
> the master will assign the region and schedule replay tasks. If the region is
> opened in a RS that does not have this conf enabled, then it will happily
> open the region in normal mode (not replay mode) causing possible (transient)
> data loss.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
