chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerome Boulon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-162) ChukwaConfiguration should handle agent and backend configuration separately
Date Mon, 20 Apr 2009 21:46:47 GMT

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

Jerome Boulon commented on CHUKWA-162:
--------------------------------------

We should be able to initialized all components by giving an existing Configuration object
or by specifying a key that will add specific resource(s). 

+1 on getting a specific configuration 
- agent - chukwa-agent-conf.xml only
- collector - hadoop-site.xml + chukwa-collector.xml 
- demux pipeline -  hadoop-site.xml + chukwa-demux-conf.xml 


Also it's not totally true that there's no sharing between data collection and data processors,
writer.hdfs.filesystem is one example.

> ChukwaConfiguration should handle agent and backend configuration separately
> ----------------------------------------------------------------------------
>
>                 Key: CHUKWA-162
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-162
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>            Reporter: Mac Yang
>
> Currently all components (both front end and back end) are forced to consume all config
files together. As a result, different components can not have different settings for the
same config parameter.

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