[
https://issues.apache.org/jira/browse/HBASE-23279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980847#comment-16980847
]
Viraj Jasani commented on HBASE-23279:
--------------------------------------
Repeated the test for 3 tables a couple of times, here are the stats:
HBASE_OFFHEAPSIZE: 5 GB
# ROW_INDEX_V1:
## Size of Blocks: 1.1 GB
## Block Count: 11510
# NONE:
## Size of Blocks: 796.5 MB
## Block Count: 12556
# ROW_INDEX_V1:
## Size of Blocks: 1.2 GB
## Block Count: 12553
# NONE:
## Size of Blocks: 796.6 MB
## Block Count: 12555
# ROW_INDEX_V1:
## Size of Blocks: 1.1 GB
## Block Count: 12864
# NONE:
## Size of Blocks: 797.1 MB
## Block Count: 12576
(Last one from previous comment)
Size of blocks seem always high for ROW_INDEX_V1.
Also, since entries in meta with encoded CFs look good during all tests, hope
we can ignore get closest at or before.
> 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
>
>
> 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)
