[
https://issues.apache.org/jira/browse/HBASE-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-11094:
----------------------------------
Release Note:
Configuration setting "hbase.master.distributed.log.replay" is only used by
Master(source of truth) and region servers which participate in recovery
process will recover region servers either in log splitting or replay mode
depending on what setting is told by Master.
When "hbase.master.distributed.log.replay" configuration setting changes,
master will wait for all existing log recovery work items drain before it
applies the new setting in order not to mix different recovery mode & ease
administrator duty to manually wait all recovery work is done and then restart
master.
> 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)
