Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 29F5F200B90 for ; Sat, 10 Sep 2016 21:40:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 28AB3160AA5; Sat, 10 Sep 2016 19:40:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9EDDA160AD2 for ; Sat, 10 Sep 2016 21:40:21 +0200 (CEST) Received: (qmail 99016 invoked by uid 500); 10 Sep 2016 19:40:20 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 98921 invoked by uid 99); 10 Sep 2016 19:40:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Sep 2016 19:40:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8D2D82C1B80 for ; Sat, 10 Sep 2016 19:40:20 +0000 (UTC) Date: Sat, 10 Sep 2016 19:40:20 +0000 (UTC) From: "Anastasia Braginsky (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 10 Sep 2016 19:40:22 -0000 [ https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15480321#comment-15480321 ] Anastasia Braginsky commented on HBASE-16417: --------------------------------------------- Hi again! As I started to explain in my previous comment, we believe this JIRA should be split into two. I have opened HBASE-16608 for this case. In HBASE-16608 we want to present the merge of the immutable segments of the pipeline into one new segment, while this is done without data-copy-compaction and without SQM. In this JIRA we plan to continue after HBASE-16608 and finalize the tuning of the in-memory flush policy for the best performance. All the performance issues are still meant to be resolved here. HBASE-16608 is for one more "algorithmic issue", not so sophisticated of course, but should resolve us the issues of two many segments (and later files) in the compaction pipeline. I would like to hear your opinion about all that! For more details look on HBASE-16608. Waiting for your fruitful thoughts! Thanks! > In-Memory MemStore Policy for Flattening and Compactions > -------------------------------------------------------- > > Key: HBASE-16417 > URL: https://issues.apache.org/jira/browse/HBASE-16417 > Project: HBase > Issue Type: Sub-task > Reporter: Anastasia Braginsky > Assignee: Anastasia Braginsky > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)