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

Hudson commented on HBASE-12562:
--------------------------------

FAILURE: Integrated in HBase-TRUNK #6218 (See 
[https://builds.apache.org/job/HBase-TRUNK/6218/])
HBASE-12562 Handling memory pressure for secondary region replicas (enis: rev 
4ac42a2f56b91ce864d1bcb04f1f9950e527aab1)
* hbase-server/src/main/java/org/apache/hadoop/hbase/io/FileLink.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/ServerRegionReplicaUtil.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegionReplayEvents.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java


> 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, hbase-12562_v2.patch, 
> hbase-12562_v2.patch, hbase-12562_v2.patch, hbase-12562_v3.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)

Reply via email to