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

Hudson commented on HBASE-17314:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-1.4 #577 (See 
[https://builds.apache.org/job/HBase-1.4/577/])
Revert "HBASE-17314 Limit total buffered size for all replication (yangzhe1991: 
rev dd0206ff319f1265fca1c6151a08dbc4e42c75f0)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
* (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java
* (delete) 
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestGlobalThrottler.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationEndpoint.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java


> Limit total buffered size for all replication sources
> -----------------------------------------------------
>
>                 Key: HBASE-17314
>                 URL: https://issues.apache.org/jira/browse/HBASE-17314
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-17314.branch-1.v01.patch, 
> HBASE-17314.branch-1.v02.patch, HBASE-17314.v01.patch, HBASE-17314.v02.patch, 
> HBASE-17314.v03.patch, HBASE-17314.v04.patch, HBASE-17314.v05.patch, 
> HBASE-17314.v06.patch
>
>
> If we have many peers or some servers have many recovered queues, we will 
> hold many entries in memory which will increase the pressure of GC, even 
> maybe OOM because we will read entries for 64MB to buffer in default for one 
> source.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to