hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anastasia Braginsky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17765) Reviving the merge possibility in the CompactingMemStore
Date Mon, 13 Mar 2017 14:10:41 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907520#comment-15907520

Anastasia Braginsky commented on HBASE-17765:

Hi [~ram_krish],

Actually I didn't increase the threshold to 30, it was 30 since we turned to use NONE, BASIC
and EAGER memstore types. For now for BASIC we actually never merge the segments, but we do
flatten the youngest segment. Here we make the threshold configurable because we see it should
be actually better to decrease this number.

> 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
> 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

View raw message