[
https://issues.apache.org/jira/browse/HBASE-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493877#comment-16493877
]
Mike Drob commented on HBASE-20390:
-----------------------------------
Thanks for updating the docs describing the new defaults, [~eshcar]! One
question about this paragraph -
{quote}
When an in-memory flush happens is calculated by dividing the configured region
flush size (Set in the table descriptor or read from
hbase.hregion.memstore.flush.size) by the number of column families and then
multiplying by hbase.memstore.inmemoryflush.threshold.factor (default is 0.014
- a little less than the size of a chunk).
{quote}
I don't see a 'chunk' defined anywhere, can we clarify what that is for readers
who may be unfamiliar?
> IMC Default Parameters for 2.0.0
> --------------------------------
>
> Key: HBASE-20390
> URL: https://issues.apache.org/jira/browse/HBASE-20390
> Project: HBase
> Issue Type: Sub-task
> Reporter: Eshcar Hillel
> Assignee: Eshcar Hillel
> Priority: Major
> Attachments: HBASE-20390-branch-2.0-01.patch,
> HBASE-20390-branch-2.0-01.patch, HBASE-20390.branch-2.0.002.patch,
> HBASE-20390.branch-2.0.003.patch, HBase 2.0 performance evaluation -
> throughput SSD_HDD.pdf, hits.ihc.png
>
>
> Setting new default parameters for in-memory compaction based on performance
> tests done in HBASE-20188
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)