chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cheng (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-253) Aggregations by User
Date Tue, 02 Jun 2009 17:33:07 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715599#action_12715599
] 

Cheng commented on CHUKWA-253:
------------------------------

Just talked to Eric. CHUKWA_IDENT_STRING might not be the right source for cluster name. Also
each chukwa instance could monitor more than one cluster. We may need a conf file to specify
all clusters.

> Aggregations by User
> --------------------
>
>                 Key: CHUKWA-253
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-253
>             Project: Hadoop Chukwa
>          Issue Type: New Feature
>            Reporter: Cheng
>         Attachments: chukwa-253-1.patch, chukwa-253.patch
>
>
> Typically a user submits jobs with similar characteristics. Aggregating the following
metrics based on users can help
> quickly identify VIP users and how their jobs look like:
> -       slot-hours used for map tasks, for reduce tasks
> -       total jobs, jobs failed
> -       data-local-maps,  rack-local-maps, remote-maps
> -       total map-input-bytes, reduce-output-records
> -       total map tasks, total reduce tasks
> The granularity of the aggregation can be as coarse as daily. Data may be used to report
top-K users in certain
> categories. Data shall be available as chukwa records (namely, one record per day per
user).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message