[
https://issues.apache.org/jira/browse/HBASE-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347436#comment-14347436
]
Hadoop QA commented on HBASE-12562:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12702261/hbase-12562_v1.patch
against master branch at commit 883d6fd8e512b14c967d2f7acf78d2b1d40e40fe.
ATTACHMENT ID: 12702261
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 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/13083//console
This message is automatically generated.
> Handling memory pressure for secondary region replicas
> ------------------------------------------------------
>
> Key: HBASE-12562
> URL: https://issues.apache.org/jira/browse/HBASE-12562
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.1.0
>
> Attachments: hbase-12562_v1.patch
>
>
> This issue will track the implementation of how to handle the memory pressure
> for secondary region replicas. Since the replicas cannot flush by themselves,
> the region server might get blocked or cause extensive flushing for its
> primary regions. The design doc attached at HBASE-11183 contains two possible
> solutions that we can pursue. The first one is to not allow secondary region
> replicas to not flush by themselves, but instead of needed allow them to
> refresh their store files on demand (which possibly allows them to drop their
> memstore snapshots or memstores). The second approach is to allow the
> secondaries to flush to a temporary space.
> Both have pros and cons, but for simplicity and to not cause extra write
> amplification, we have implemented the first approach. More details can be
> found in the design doc, but we can also discuss other options here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
