hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11094) Distributed log replay is incompatible for rolling restarts
Date Fri, 13 Jun 2014 17:09:03 GMT

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

stack commented on HBASE-11094:

bq. Once 1.0 branch is cut, I'll create a JIRA to turn distributedLogReplay off by default
depends on the rolling upgrade story for 1.0. 

What does the above mean [~jeffreyz]?

Can you add a release note saying what has been implemented?  I know you say '(basically no
release note for the JIRA)' above but would be good for us devs trying to follow along (or
who may have to debug it in future).  Please describe what was implemented

To be clear, mode is LOG_REPLAY currently in master?

Reading over the patch, it looks good.  I'm not sure I am clear on all that is going on but
I like the sound of it (smile).

> 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

View raw message