[
https://issues.apache.org/jira/browse/HBASE-16401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648305#comment-15648305
]
ramkrishna.s.vasudevan commented on HBASE-16401:
------------------------------------------------
Working on one of the subtasks of offheap write path. WE may have to do two
things before we enable it in 2.0
-> If we have offheap write path support do not auto tune memstore size. As
offheap memstore is adding a new config for global.offheap.memstore.size - this
heap memory tuner is going to adjust the memstore size on heap. It may or may
not be relevant.
-> Add support in such a way that based on the flush request, we should
determine if the flush happened due to offheap global memstore limit or was it
due to the memstore heap limit ( that happens due to references). How ever, in
case of offheap generally we won't be hitting the memstore heap limit and in
that case decreasing the global memstore heap percent is not ideally correct
which may also lead to decrease in memstore chunk pool size.
> Enable HeapMemoryManager by default in 2.0
> ------------------------------------------
>
> Key: HBASE-16401
> URL: https://issues.apache.org/jira/browse/HBASE-16401
> Project: HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Blocker
> Fix For: 2.0.0
>
>
> Back in HBASE-5349, on the end of the issue, we talked about enabling
> HeapMemoryManager by default. Lets do it for 2.0 with some conservative
> boundaries. Do it now so we have some experience running it before release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
