[
https://issues.apache.org/jira/browse/HBASE-17314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763588#comment-15763588
]
Phil Yang commented on HBASE-17314:
-----------------------------------
bq. How is the above determined ?
Now we have a 64MB max buffered size per peer, so the total buffered size can
be larger but can not too large.
bq. Where is the above variable incremented ?
It is gotten by each ReplicationSource and increment/decrement by them.
> Limit total buffered size for all replication sources
> -----------------------------------------------------
>
> Key: HBASE-17314
> URL: https://issues.apache.org/jira/browse/HBASE-17314
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: Phil Yang
> Assignee: Phil Yang
> Attachments: HBASE-17314.v01.patch, HBASE-17314.v02.patch,
> HBASE-17314.v03.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)
