[
https://issues.apache.org/jira/browse/CHUKWA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Boulon updated CHUKWA-12:
--------------------------------
Attachment: CHUKWA-12-3.patch
Previous patch didn't apply because of CHUKWA-65 (hadoop metrics log files
should be managed more cleanly).
On top my prevous comments my patch:
- Remove all changes made to Log4JMetricsContext.java from CHUKWA-65
- Delete conf/chukwa-hadoop-metrics-log4j.properties
---> remove dependency on an external log4j file
(conf/chukwa-hadoop-metrics-log4j.properties) everything is done via
hadoop-metrics.properties since there's a well defined way to pass parameters
to the MetricContext class
- Use JAVA API to set Read/Write permission (RW for ALL since another user need
to delete the file see: CHUKWA-65 )
--> this part is still not "clean" in my mind since anyone can RW ... but I
don't have a better idea for now
- Move conf/hadoop-metrics.properties to conf/hadoop-metrics.properties.template
- Fix bin/VERSION
> Add instrumentation Api for Chukwa components
> ---------------------------------------------
>
> Key: CHUKWA-12
> URL: https://issues.apache.org/jira/browse/CHUKWA-12
> Project: Hadoop Chukwa
> Issue Type: New Feature
> Reporter: Jerome Boulon
> Assignee: Jerome Boulon
> Priority: Blocker
> Attachments: CHUKWA-12-2.patch, CHUKWA-12-3.patch, CHUKWA-12.patch,
> chukwa12 errors.txt
>
>
> Chukwa Components should be able to emit some metrics in an easy way.
> I'm thinking of reusing the new HADOOP JMX instrumentation API to do that +
> MetricsContext to output/collect them using chukwa.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
