[
https://issues.apache.org/jira/browse/HBASE-11511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061485#comment-14061485
]
Hadoop QA commented on HBASE-11511:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12655645/hbase-11511_v3.patch
against trunk revision .
ATTACHMENT ID: 12655645
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/10062//console
This message is automatically generated.
> Write flush events to WAL
> -------------------------
>
> Key: HBASE-11511
> URL: https://issues.apache.org/jira/browse/HBASE-11511
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.99.0, 2.0.0
>
> Attachments: hbase-11511_v1.patch, hbase-11511_v1.patch,
> hbase-11511_v2.patch, hbase-11511_v3.patch
>
>
> We used to write COMPLETE_FLUSH event to WAL until it got removed in 0.96 in
> issue HBASE-7329.
> For secondary region replicas, it is important to share the data files with
> the primary region. So we should reintroduce the flush wal markers so that
> the secondary region replicas can pick up the newly flushed files from the
> WAL and start serving data from those.
> A design doc which explains the context a bit better can be found in
> HBASE-11183.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
