Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 28 May 2011 15:11:47 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1367220442.50924.1306595507419.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <422229425.46279.1306434947359.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-3927) display total uncompressed byte size
 of a region in web UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu updated HBASE-3927:
--------------------------

    Attachment: 3927.txt

This version adds compression ratio in HServerLoad.toString()

> display total uncompressed byte size of a region in web UI
> ----------------------------------------------------------
>
>                 Key: HBASE-3927
>                 URL: https://issues.apache.org/jira/browse/HBASE-3927
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: Matt Corgan
>            Assignee: Ted Yu
>            Priority: Minor
>         Attachments: 3927.txt, regionserver-showing-compression-ratio.png
>
>
> The decision to split data blocks when flushing and compacting is made based on the uncompressed data size which can often lead to compressed disk blocks that are a fraction of the intended 64 KB (default).  This often leads to a larger number of blocks and index entries than expected and can cause block indexes to take up GB of memory.
> There is already a "long totalUncompressedBytes" written to the HFileTrailer.  It would be nice to expose this in the web UI to make it easier to calculate the compression ratio and then raise the block size appropriately (not necessarily to get it back to 64K).
> This should probably be added wherever the other HFile metrics are: RegionLoad.createRegions(..), and HServerLoad.  HServerLoad is a Writable, so it may break serialization.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira