Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5F910CB21 for ; Mon, 17 Mar 2014 16:03:28 +0000 (UTC) Received: (qmail 82017 invoked by uid 500); 17 Mar 2014 16:03:23 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 81447 invoked by uid 500); 17 Mar 2014 16:03:21 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 81435 invoked by uid 99); 17 Mar 2014 16:03:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2014 16:03:21 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.213.53 as permitted sender) Received: from [209.85.213.53] (HELO mail-yh0-f53.google.com) (209.85.213.53) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2014 16:03:15 +0000 Received: by mail-yh0-f53.google.com with SMTP id v1so5490898yhn.12 for ; Mon, 17 Mar 2014 09:02:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GObpwVtiKw1v6NnXVnhx080qgIVTbswGaMBJMXLTyP8=; b=uE5ksRNRr3/Ae96h+1PuJzIvvmoLyg5df/58h8hu6I+3HJ5j5FJqAct9ZadxFMblT9 jlp04wDKUWq4Kn3x/G73fSlesAeFPJj/15xiUeqTZJrquSBrfAQPClwX1Qxg6VyBgJKZ xOnlf0MO1AToLxpERhK2Ypl5xhLsUXxuqhVM5qt8mdiEvkJXoDRZ3QCFd+nr2XJ5y9wy U3hFda919IsmewZxJ+B6Tbd4+NBSgVf0Jt186fKIODDTuTMU756PU4NYvPXKfFD7QWSj u2+g2wHRBoaE+z/1bksK8b5Hw1XpcarJ5rT27K8WAr24JGroEqjTgbLT97yoj1lDw3Je iVOw== MIME-Version: 1.0 X-Received: by 10.236.130.37 with SMTP id j25mr3835141yhi.106.1395072174371; Mon, 17 Mar 2014 09:02:54 -0700 (PDT) Received: by 10.170.79.86 with HTTP; Mon, 17 Mar 2014 09:02:54 -0700 (PDT) In-Reply-To: References: Date: Mon, 17 Mar 2014 09:02:54 -0700 Message-ID: Subject: Re: block cache size questions From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=20cf3011dff563b7b904f4cf8dd0 X-Virus-Checked: Checked by ClamAV on apache.org --20cf3011dff563b7b904f4cf8dd0 Content-Type: text/plain; charset=ISO-8859-1 For #1, see http://stackoverflow.com/questions/4667483/how-is-the-default-java-heap-size-determined For #3, it is currently not possible. Cheers On Mon, Mar 17, 2014 at 6:01 AM, Linlin Du wrote: > Hi all, > > First question: > According to documentation, hfile.block.cache.size is by default 40 > percentage of maximum heap (-Xmx setting). If -Xmx is not used and only > -Xms is used, what will it be in this case? > > Second question: > This 40% heap space is shared by all entities (stores). How much block > cache is used by each store (entity)? Is it allocated on demand? If a > region has never been read after the region server is up, will block cache > be allocated for it? > > Third question: > Is it possible to tell from .META when a region was last read? If so, how? > > Many thanks, > > Linlin > > > > > --20cf3011dff563b7b904f4cf8dd0--