Return-Path: 
 <issues-return-221011-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
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 97A8D187AA
	for <apmail-hbase-issues-archive@www.apache.org>;
 Wed, 18 Nov 2015 23:14:12 +0000 (UTC)
Received: (qmail 24386 invoked by uid 500); 18 Nov 2015 23:14:11 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 24264 invoked by uid 500); 18 Nov 2015 23:14:11 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 23957 invoked by uid 99); 18 Nov 2015 23:14:11 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Nov 2015 23:14:11 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 1F2552C1F5E
	for <issues@hbase.apache.org>; Wed, 18 Nov 2015 23:14:11 +0000 (UTC)
Date: Wed, 18 Nov 2015 23:14:11 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12914287.1447888435000.113926.1447888451124@Atlassian.JIRA>
In-Reply-To: <JIRA.12914287.1447888435000@Atlassian.JIRA>
References: <JIRA.12914287.1447888435000@Atlassian.JIRA>
 <JIRA.12914287.1447888435520@arcas>
Subject: [jira] [Created] (HBASE-14836) Document how to deal with WARN
 "BucketCache: Failed allocation for
 c326ba1d8a134b4487539239fce60a99_0;...too big size=1113254; adjust
 BucketCache sizes hbase.bucketcache.bucket.sizes to accomodate if size
 seems reasonable and you want it cached."
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

stack created HBASE-14836:
-----------------------------

             Summary: Document how to deal with WARN "BucketCache: Failed allocation for c326ba1d8a134b4487539239fce60a99_0;...too big size=1113254; adjust BucketCache sizes hbase.bucketcache.bucket.sizes to accomodate if size seems reasonable and you want it cached."
                 Key: HBASE-14836
                 URL: https://issues.apache.org/jira/browse/HBASE-14836
             Project: HBase
          Issue Type: Bug
          Components: BucketCache, BlockCache
            Reporter: stack


A busy, internal *smart* user was having their logs filled with messages like this:

{code}
BucketCache: Failed allocation for c326ba1d8a134b4487539239fce60a99_0; org.apache.hadoop.hbase.io.hfile.bucket.BucketAllocatorException: Allocation too big size=1113254; adjust BucketCache sizes hbase.bucketcache.bucket.sizes to accomodate if size seems reasonable and you want it cached.
{code}

.. and wasn't sure how to address them.

Had to explain what the above is about (we don't have a bucket of a size into which we could put this object).

Need to doc that c326ba1d8a134b4487539239fce60a99_0 is a filename and an offset. Need to doc how to look at this object that we are trying to cache using hfile tool.

Then had to describe how you'd add a bucket that was big enough. Below I add 786432 and 1048576 beyond the default bucket sizes.

<property>
<name>hbase.bucketcache.bucket.sizes</name>
<value>4096, 8192, 16384, 32768, 40960, 49152, 57344, 65536, 98304, 131072, 196608, 262144, 393216, 524288, 786432, 1048576</value>
</property>

The operator asked some questions about how can I tell rates at which Cell sizes are being served.

Also, we were looking at the bucket numbers in the bucket L2 tab and it became obvious that bucket sizes, accesses, and frees should be summary stats, not per bucket instance. TODO.

Anyway, this issue is about doc'ing how to deal w/ the above.  We'll see it more when bucket cache is on always as we'd like to do in 2.0 hbase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)