Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 20 Apr 2016 21:24:25 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12958301.1460503711000.283400.1461187465455@Atlassian.JIRA>
In-Reply-To: <JIRA.12958301.1460503711000@Atlassian.JIRA>
References: <JIRA.12958301.1460503711000@Atlassian.JIRA>
 <JIRA.12958301.1460503711909@arcas>
Subject: [jira] [Commented] (HBASE-15640) L1 cache doesn't give fair warning
 that it is showing partial stats only when it hits limit
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-15640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250739#comment-15250739 ] 

Elliott Clark commented on HBASE-15640:
---------------------------------------

Thanks [~stack]

> L1 cache doesn't give fair warning that it is showing partial stats only when it hits limit
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-15640
>                 URL: https://issues.apache.org/jira/browse/HBASE-15640
>             Project: HBase
>          Issue Type: Sub-task
>          Components: BlockCache
>            Reporter: stack
>            Assignee: stack
>         Attachments: Screen Shot 2016-04-12 at 4.21.50 PM.png, bc.ui (1).patch, bc.ui.patch, bc.ui.v3.patch, bc.ui.v4.patch
>
>
> I was baffled looking at L1 Cache because it was stuck at 100k blocks and only 'loading' 3G of data according to the UI. When I looked in log, all the numbers looked write in the Cache summary reported in log.
> Turns out our buckecache UI template will cut off calculating stats at a limit --which is probably what we want -- but the fact that it has done this should be more plain.


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