Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9F806200C5B for ; Wed, 15 Mar 2017 03:13:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9E395160B7E; Wed, 15 Mar 2017 02:13:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ECD9E160B89 for ; Wed, 15 Mar 2017 03:13:45 +0100 (CET) Received: (qmail 91490 invoked by uid 500); 15 Mar 2017 02:13:45 -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 91469 invoked by uid 99); 15 Mar 2017 02:13:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Mar 2017 02:13:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 450571A0187 for ; Wed, 15 Mar 2017 02:13:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id NKPwF3hZcDMy for ; Wed, 15 Mar 2017 02:13:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 376AE5FB6B for ; Wed, 15 Mar 2017 02:13:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id EA3E1E08C3 for ; Wed, 15 Mar 2017 02:13:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9C810243A8 for ; Wed, 15 Mar 2017 02:13:41 +0000 (UTC) Date: Wed, 15 Mar 2017 02:13:41 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 15 Mar 2017 02:13:46 -0000 [ https://issues.apache.org/jira/browse/HBASE-17780?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D159= 25426#comment-15925426 ]=20 Hudson commented on HBASE-17780: -------------------------------- SUCCESS: Integrated in Jenkins build HBase-1.4 #671 (See [https://builds.ap= ache.org/job/HBase-1.4/671/]) HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell:= rev d7666b60662cfc8492e396565b29494407c7843c) * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteB= ufferPool.java > 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: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31 > > Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch > > > This comment in=C2=A0BoundedByteBufferPool talks about "At capacity ..." = warnings 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 = just let the ByteBuffer go > =C2=A0* rather than add it to the pool. If more ByteBuffers than the conf= igured maximum instances, > =C2=A0* we will not add the passed ByteBuffer to the pool; we will just d= rop 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 an= d 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)