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, 20 Mar 2017 08:31:41 GMT

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

Anastasia Braginsky commented on HBASE-17765:
---------------------------------------------

[~stack], thanks for taking a look :)

The merging is existing possibility in the code and will happen if we change COMPACTING_MEMSTORE_THRESHOLD_DEFAULT
in the code or hbase.hregion.compacting.memstore.threshold in the hbase-site to be less than
4. This JIRA intends to fixs bugs in merge and make it configurable. Under HBASE-16417 there
is a discussion whether to make the merge part of the default configuration or not. This JIRA
doesn't turn the merge into default. I am adding now a merge test to this patch and soon is
going to publish a new patch.

> 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
(v6.3.15#6346)

Mime
View raw message