chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saisai Shao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CHUKWA-667) Optimize the HBase schema for Ganglia queris
Date Mon, 15 Oct 2012 08:52:04 GMT

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

Saisai Shao updated CHUKWA-667:
-------------------------------

    Description: 
Chukwa HBase table schema is designed for HICC, it cannot be fully adapted to Ganglia web
frontend for several reasons:
(1) cannot fastly retrieve all the cluster and related host names.
(2) system metrics have no attributes, like type, unit, so it is hard to explain the collected
metrics by code.
(3) lack of data cosolidate function, choosing metric for a large time range (like 30 days)
will fetch all the data and draw graph, which will largely lose performance.

We will redesign the table schema that will be better adapted to Ganglia web frontend queries.

  was:
Chukwa HBase table schema is designed for HICC, it cannot be fully adapted to Ganglia web
frontend for several reasons:
(1) cannot fastly retrieve all the cluster and related host names.
(2) system metrics have no attributes, like type, unit, so it is hard to explain the collected
metrics by code.
(3) lack of data cosolidate function, choosing metric for a large time range (like 30 days)
will fetch all the data and draw graph, which will largely lose performance.

    
> Optimize the HBase schema for Ganglia queris
> --------------------------------------------
>
>                 Key: CHUKWA-667
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-667
>             Project: Chukwa
>          Issue Type: Sub-task
>          Components: Data Processors
>    Affects Versions: 0.6.0
>            Reporter: Saisai Shao
>
> Chukwa HBase table schema is designed for HICC, it cannot be fully adapted to Ganglia
web frontend for several reasons:
> (1) cannot fastly retrieve all the cluster and related host names.
> (2) system metrics have no attributes, like type, unit, so it is hard to explain the
collected metrics by code.
> (3) lack of data cosolidate function, choosing metric for a large time range (like 30
days) will fetch all the data and draw graph, which will largely lose performance.
> We will redesign the table schema that will be better adapted to Ganglia web frontend
queries.

--
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

Mime
View raw message