[
https://issues.apache.org/jira/browse/HBASE-23279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024332#comment-17024332
]
Anoop Sam John commented on HBASE-23279:
----------------------------------------
bq.milarly if the next available bucket is 96K you mean it will not use the
full 96K and so it will waste the buckets?
Yes
For this changing the defaults of bucket cache may help?
Ya. This was discussed. Instead we should correct this ROW_INDEX DBE also to
account the encoded data size and honor the block size. There is no way to
predict the size of the index data per block because it depends on #rows in a
block. So any such calc for changing the block size wont be effective.
> Switch default block encoding to ROW_INDEX_V1
> ---------------------------------------------
>
> Key: HBASE-23279
> URL: https://issues.apache.org/jira/browse/HBASE-23279
> Project: HBase
> Issue Type: Wish
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Lars Hofhansl
> Assignee: Viraj Jasani
> Priority: Minor
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HBASE-23279.master.000.patch,
> HBASE-23279.master.001.patch, HBASE-23279.master.002.patch,
> HBASE-23279.master.003.patch, HBASE-23279.master.004.patch,
> HBASE-23279.master.005.patch
>
>
> Currently we set both block encoding and compression to NONE.
> ROW_INDEX_V1 has many advantages and (almost) no disadvantages (the hfiles
> are slightly larger about 3% or so). I think that would a better default than
> NONE.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
