Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Aug 2014 17:37:13 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12541706.1328654190992.44768.1407519433423@arcas>
In-Reply-To: <JIRA.12541706.1328654190992@arcas>
References: <JIRA.12541706.1328654190992@arcas>
Subject: [jira] [Commented] (HBASE-5349) Automagically tweak global memstore
 and block cache sizes based on workload
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-5349:
------------------------------

[~anoop.hbase] I think we should enable by default, at least in master branch. What you think?  A policy that sizes the blockcache so there are no evictions OR we hit maxsize would be sweet.  I could add that.

> Automagically tweak global memstore and block cache sizes based on workload
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-5349
>                 URL: https://issues.apache.org/jira/browse/HBASE-5349
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.92.0
>            Reporter: Jean-Daniel Cryans
>            Assignee: Anoop Sam John
>             Fix For: 0.99.0
>
>         Attachments: HBASE-5349_V2.patch, HBASE-5349_V3.patch, HBASE-5349_V4.patch, HBASE-5349_V5.patch, WIP_HBASE-5349.patch
>
>
> Hypertable does a neat thing where it changes the size given to the CellCache (our MemStores) and Block Cache based on the workload. If you need an image, scroll down at the bottom of this link: http://www.hypertable.com/documentation/architecture/
> That'd be one less thing to configure.


--
This message was sent by Atlassian JIRA
(v6.2#6252)