Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D0F9AFC for ; Thu, 5 Jul 2012 23:31:37 +0000 (UTC) Received: (qmail 89006 invoked by uid 500); 5 Jul 2012 23:31:35 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 88964 invoked by uid 500); 5 Jul 2012 23:31:35 -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 88898 invoked by uid 99); 5 Jul 2012 23:31:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 23:31:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id AA0E1142852 for ; Thu, 5 Jul 2012 23:31:35 +0000 (UTC) Date: Thu, 5 Jul 2012 23:31:35 +0000 (UTC) From: "Jason Dai (JIRA)" To: issues@hbase.apache.org Message-ID: <1661451831.11670.1341531095698.JavaMail.jiratomcat@issues-vm> In-Reply-To: <652064642.383.1341295742165.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6312) Make BlockCache eviction thresholds configurable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407600#comment-13407600 ] Jason Dai commented on HBASE-6312: ---------------------------------- I think there are two different questions here: 1) Performance - whether the current values of acceptable & minimum factors make sense. It seems nobody has definitive answers, and maybe we should make these more aggressive and at least make the minimum configurable for people to experiment, just as J-D proposed. 2) User experience - whether the hfile.block.cache.size parameter provides the proper behaviors as the user would expect. It seems that most of the time the user can only use the memory size of hfile.block.cache.size * acceptable factor, which could be very confusing as the user is not aware of acceptable factor at all. What I proposed above is to evict when the cache size > hfile.block.cache.size, and block if cache size > hfile.block.cache.size * (1 + acceptable factor). > Make BlockCache eviction thresholds configurable > ------------------------------------------------ > > Key: HBASE-6312 > URL: https://issues.apache.org/jira/browse/HBASE-6312 > Project: HBase > Issue Type: Improvement > Components: io > Affects Versions: 0.94.0 > Reporter: Jie Huang > Priority: Minor > Attachments: hbase-6312.patch > > > Some of our customers found that tuning the BlockCache eviction thresholds made test results different in their test environment. However, those thresholds are not configurable in the current implementation. The only way to change those values is to re-compile the HBase source code. We wonder if it is possible to make them configurable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira