[
https://issues.apache.org/jira/browse/HBASE-17757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900902#comment-15900902
]
Anoop Sam John edited comment on HBASE-17757 at 3/8/17 8:24 AM:
----------------------------------------------------------------
Ya u are correct. The size is encodedSize only that u newly track.
It is not single row we try keep in one block only. It is the same cell. See
checkKey(). Ya still it is not 100%.. My Q was is it better. Any way that is
another topic.
Seems like in encoding case, ur proposal will make the situation much much
better.
was (Author: anoop.hbase):
Ya u are correct. The size is encodedSize only that u newly track.
It is not single row we try keep in one block only. It is the same cell. See
checkKey(). Ya still it is not 100%.. My Q was is it better.
> Unify blocksize after encoding to decrease memory fragment
> -----------------------------------------------------------
>
> Key: HBASE-17757
> URL: https://issues.apache.org/jira/browse/HBASE-17757
> Project: HBase
> Issue Type: New Feature
> Reporter: Allan Yang
> Assignee: Allan Yang
> Attachments: HBASE-17757.patch
>
>
> Usually, we store encoded block(uncompressed) in blockcache/bucketCache.
> Though we have set the blocksize, after encoding, blocksize is varied. Varied
> blocksize will cause memory fragment problem, which will result in more FGC
> finally.In order to relief the memory fragment, This issue adjusts the
> encoded block to a unified size.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
