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

Ari Rabkin commented on CHUKWA-315:
-----------------------------------

The current setup is definitely confusing.  Files that go in hadoop conf should 
be very clearly separate from chukwa config files.
And it's not quite clear to me that we want anything as complicated as the 
Hadoop metrics framework for monitoring chukwa.

> hadoop-metrics.properties has double meaning in chukwa
> ------------------------------------------------------
>
>                 Key: CHUKWA-315
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-315
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: build and test code
>    Affects Versions: 0.2.0
>         Environment: Redhat EL 5.1, Java 6
>            Reporter: Eric Yang
>
> "hadoop-metrics.properties" is used as the sample for collecting hadoop 
> metrics through chukwa.  It is also used by chukwa process to send out chukwa 
> metrics.  Hence, when people copy hadoop-metrics.properties from chukwa 
> source code, it needs to be hand modified to comment out chukwa metrics.  
> When it is left in chukwa conf dir, it needs to have hadoop section commented 
> out.  This is not very user friendly, and should be addressed.
> I am not comfortable to use hadoop metrics context as the metrics generation 
> tools for chukwa.  Metrics context class is a specialized tool for hadoop to 
> emite metrics.  By using hadoop metrics context, It ties unnecessary 
> component into chukwa and complicates ease of use.  I vote to remove metrics 
> context from chukwa.

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

Reply via email to