Return-Path: 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 E510F101F4 for ; Wed, 10 Apr 2013 01:05:13 +0000 (UTC) Received: (qmail 56978 invoked by uid 500); 10 Apr 2013 01:05:13 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 56946 invoked by uid 500); 10 Apr 2013 01:05:13 -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 56934 invoked by uid 99); 10 Apr 2013 01:05:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Apr 2013 01:05:13 +0000 Date: Wed, 10 Apr 2013 01:05:13 +0000 (UTC) From: "Daisuke Kobayashi (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-8315) Documentation should have more information of LRU Stats MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Daisuke Kobayashi created HBASE-8315: ---------------------------------------- Summary: Documentation should have more information of LRU Stats Key: HBASE-8315 URL: https://issues.apache.org/jira/browse/HBASE-8315 Project: HBase Issue Type: Improvement Components: documentation Affects Versions: 0.95.0 Reporter: Daisuke Kobayashi Unfortunately, there's no documentation to explain the meaning of each LRU Stats in the regionserver logs. So this is for creating a new paragraph regarding this. My current idea is below, but it's a little bit difficult to explain the difference between 'cachingAccesses' and 'accesses' from an administrator or a user views. Could you guys help to improve the content? {noformat} total: The current memory size of the cache in use. free: The total free memory currently available to store more cache entries. max: Maximum allowed memory size of the cache. blocks: Caches store blocks of data; this number is the current # of blocks stored, which use up the "total" memory space. accesses: The total number of times the cache was accessed, regardless of result. hits: The total number of times the cache was accessed and the result was a successful hit (presence of looked up element in cache is a hit). hitRatio: The current percentage for "hits / accesses". ==== Unclear: cachingAccesses: cachingHits + The number of getBlock requests that were cache misses, but only from requests that were set to use the block cache. cachingHits: The number of getBlock requests that were cache hits, but only from requests that were set to use the block cache. This is because all reads ===== cachingHitsRatio: The current percentage for "cachintHits / cachingAccesses" evictions: The total number of times an eviction has occurred (based on the use of the LRU algorithm) evicted: The total number of blocks that have been evicted (based on the use of the LRU algorithm) evictedPerRun: The total number of blocks that have been evicted overall / The number of times an eviction has occurred overall {noformat} And also, where should we add this paragraph in the documentation? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira