[
https://issues.apache.org/jira/browse/HBASE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671677#action_12671677
]
stack commented on HBASE-823:
-----------------------------
Luo: On 1., there is also the HADOOP-3856 tactic that Andrew Purtell is working
on to get over the xceiver limit and work in HBASE-61 should shrink index size
in heap dramatically but even then your point stands, that we need to be
counting the indices and capping their size. Your HBASE-24 patch where we
limit number of open store files is probably only avenue open to us until
HADOOP-3856 is done (Its a blocker on 0.20.0 hbase).
> Concurrent "open mapfile reader" limit
> --------------------------------------
>
> Key: HBASE-823
> URL: https://issues.apache.org/jira/browse/HBASE-823
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Blocker
> Fix For: 0.20.0
>
>
> Over in HBASE-745, Luo Ning profiling found that the number of open Readers
> has direct impact on memory used. This issue is about putting an upper bound
> on the number of open Readers doing something like a bounded pool w/ a LRU
> eviction policy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
