You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2017/11/30 01:11:00 UTC
[jira] [Commented] (HBASE-17314) Limit total buffered size for all
replication sources
[ https://issues.apache.org/jira/browse/HBASE-17314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271946#comment-16271946 ]
Andrew Purtell commented on HBASE-17314:
----------------------------------------
I reverted this from branch-1.4 because it's test was broken by a revert of HBASE-9465 on same branch, see HBASE-19381
> 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.5.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.4.14#64029)