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 77935200CDF for ; Tue, 25 Jul 2017 19:54:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7616816289A; Tue, 25 Jul 2017 17:54:06 +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 BF9F416289C for ; Tue, 25 Jul 2017 19:54:05 +0200 (CEST) Received: (qmail 25342 invoked by uid 500); 25 Jul 2017 17:54:04 -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 25265 invoked by uid 99); 25 Jul 2017 17:54:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2017 17:54:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 920B6C1839 for ; Tue, 25 Jul 2017 17:54:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id gd988uTOaeVb for ; Tue, 25 Jul 2017 17:54:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2FCFA5FBEA for ; Tue, 25 Jul 2017 17:54:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 03989E08B4 for ; Tue, 25 Jul 2017 17:54:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 269C523F0D for ; Tue, 25 Jul 2017 17:54:00 +0000 (UTC) Date: Tue, 25 Jul 2017 17:54:00 +0000 (UTC) From: "Anoop Sam John (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11206) Enable automagically tweaking memstore and blockcache sizes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 25 Jul 2017 17:54:06 -0000 [ https://issues.apache.org/jira/browse/HBASE-11206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100442#comment-16100442 ] Anoop Sam John commented on HBASE-11206: ---------------------------------------- We can. As Nick pointed above, it works with on heap things only. This is HeapMemory tuner. So the Memstore (MSLAB) and BC both in on heap. Now we have off heap support for both these in 2.0. But there is not auto tuner for off heap. But any way another story and can be done later. This can be helpful for those who use both on heap. > Enable automagically tweaking memstore and blockcache sizes > ----------------------------------------------------------- > > Key: HBASE-11206 > URL: https://issues.apache.org/jira/browse/HBASE-11206 > Project: HBase > Issue Type: Task > Reporter: stack > Assignee: stack > > HBASE-5349 > "Automagically tweak global memstore and block cache sizes based on workload" adds a nice new feature. It is off by default. Lets turn it on for 0.99. Liang Xie is concerned that automatically shifting blockcache and memstore sizes could wreck havoc w/ GC'ing in low-latency serving situation -- a valid concern -- but lets enable this feature in 0.99 and see how it does. Can always disable it before 1.0 if a problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)