Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 13 Mar 2017 23:51:41 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13055773.1489449073000.8417.1489449101533@Atlassian.JIRA>
In-Reply-To: <JIRA.13055773.1489449073000@Atlassian.JIRA>
References: <JIRA.13055773.1489449073000@Atlassian.JIRA> <JIRA.13055773.1489449073280@jira-lw-us.apache.org>
Subject: [jira] [Created] (HBASE-17780) BoundedByteBufferPool "At capacity"
 messages are not actionable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 13 Mar 2017 23:51:46 -0000

Andrew Purtell created HBASE-17780:
--------------------------------------

             Summary: BoundedByteBufferPool "At capacity" messages are not =
actionable
                 Key: HBASE-17780
                 URL: https://issues.apache.org/jira/browse/HBASE-17780
             Project: HBase
          Issue Type: Bug
    Affects Versions: 1.3.0
            Reporter: Andrew Purtell
            Assignee: Andrew Purtell
            Priority: Minor
             Fix For: 1.31, 2.0.0, 1.4.0


This comment in=C2=A0BoundedByteBufferPool talks about "At capacity ..." wa=
rnings from this class that may appear in logs when under load:

{code}
=C2=A0* If a ByteBuffer is bigger than the configured threshold, we will ju=
st let the ByteBuffer go
=C2=A0* rather than add it to the pool. If more ByteBuffers than the config=
ured maximum instances,
=C2=A0* we will not add the passed ByteBuffer to the pool; we will just dro=
p it
=C2=A0* (we will log a WARN in this case that we are at capacity).
{code}

First, dropping buffers when the pool is full is obviously an expected and =
normal condition. Second, there is nothing actionable about that warning.=
=C2=A0Might be useful for developers, perhaps. Drop it to DEBUG.=20


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)