Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 25A07CD5E for ; Thu, 7 Aug 2014 17:34:19 +0000 (UTC) Received: (qmail 5218 invoked by uid 500); 7 Aug 2014 17:34:16 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 5135 invoked by uid 500); 7 Aug 2014 17:34:16 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 5067 invoked by uid 99); 7 Aug 2014 17:34:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Aug 2014 17:34:16 +0000 Date: Thu, 7 Aug 2014 17:34:16 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-11697) Improve the 'Too many blocks' message on UI blockcache status page MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andrew Purtell created HBASE-11697: -------------------------------------- Summary: Improve the 'Too many blocks' message on UI blockcache status page Key: HBASE-11697 URL: https://issues.apache.org/jira/browse/HBASE-11697 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell Priority: Minor Fix For: 0.99.0, 2.0.0, 0.98.6 Attachments: TooManyBlocks.png If metrics calculations over blockcache contents stopped after examining hbase.ui.blockcache.by.file.max items, the UI will put up a message. However, this notion of "too many blocks" / fullness refers to structures used for calculating blockcache metrics. See BlockCacheUtil. We should improve this message so it does not leave a user the impression the blockcache may be in a bad state. -- This message was sent by Atlassian JIRA (v6.2#6252)