[
https://issues.apache.org/jira/browse/HBASE-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939746#comment-15939746
]
Anoop Sam John commented on HBASE-17765:
----------------------------------------
Patch looks good.
{code}
public static final String COMPACTING_MEMSTORE_THRESHOLD_KEY =
51 "hbase.hregion.compacting.memstore.threshold";
{code}
Am not sure whether this name is correct. This is a threshold value for
#segments above which there will be in memory merge. So seeing this one may
not get what threshold it is. Compacting memstore will have threshold for in
memory flush also (Segment flush to pipeline)/ So pls give a better/clear name.
> Reviving the merge possibility in the CompactingMemStore
> --------------------------------------------------------
>
> Key: HBASE-17765
> URL: https://issues.apache.org/jira/browse/HBASE-17765
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anastasia Braginsky
> Assignee: Anastasia Braginsky
> Fix For: 2.0.0
>
> Attachments: HBASE-17765-V01.patch, HBASE-17765-V02.patch,
> HBASE-17765-V03.patch
>
>
> According to the new performance results presented in the HBASE-16417 we see
> that the read latency of the 90th percentile of the BASIC policy is too big
> due to the need to traverse through too many segments in the pipeline. In
> this JIRA we correct the bug in the merge sizing calculations and allow
> pipeline size threshold to be a configurable parameter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
