[
https://issues.apache.org/jira/browse/HBASE-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333893#comment-15333893
]
Dave Latham commented on HBASE-15950:
-------------------------------------
I share the concerns with Mikhail - I don't think we should risk breaking
clusters that have been tuned on a minor version upgrade, whether it's 1.3 or
1.4. I think having "hbase.memorylayout.use.unsafe" false by default in the
minor release would be safer and turn it on in a major release.
> Fix memstore size estimates to be more tighter
> ----------------------------------------------
>
> Key: HBASE-15950
> URL: https://issues.apache.org/jira/browse/HBASE-15950
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.4.0
>
> Attachments: Screen Shot 2016-06-02 at 8.48.27 PM.png,
> hbase-15950-v0.patch, hbase-15950-v1.patch, hbase-15950-v2.branch-1.patch,
> hbase-15950-v2.branch-1.patch, hbase-15950-v2.patch
>
>
> While testing something else, I was loading a region with a lot of data.
> Writing 30M cells in 1M rows, with 1 byte values.
> The memstore size turned out to be estimated as 4.5GB, while with the JFR
> profiling I can see that we are using 2.8GB for all the objects in the
> memstore (KV + KV byte[] + CSLM.Node + CSLM.Index).
> This obviously means that there is room in the write cache that we are not
> effectively using.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
