[
https://issues.apache.org/jira/browse/CHUKWA-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842024#action_12842024
]
Bill Graham commented on CHUKWA-460:
------------------------------------
Testing the collector it appears it does not have this dependency, but instead
picks up the HDFS configs correctly from the hadoop configs. Which is good,
albeit confusing.
So really this config should be moved to the demux configs for now, to clear up
potential confusion over who reads that value. Or better yet, Eric's approach
of removing the config entirely and fixing Demux to not use that value should
be followed.
> Demux depends on conf/chukwa-collector-conf.xml
> -----------------------------------------------
>
> Key: CHUKWA-460
> URL: https://issues.apache.org/jira/browse/CHUKWA-460
> Project: Hadoop Chukwa
> Issue Type: Bug
> Components: Data Processors
> Reporter: Eric Yang
> Assignee: Eric Yang
>
> We've packaged our own chukwa rpms to be able to deploy the collector, the
> agent and the data processor each separately. In doing so I realized that the
> data processor (i.e., Demux) has a dependency on
> conf/chukwa-collector-conf.xml as packaged in the distro, since that's the
> only place where where 'writer.hdfs.filesystem' is set.
> The workaround is straight forward enough (just add writer.hdfs.filesystem to
> chukwa-demux.xml), but I thought I'd point out the cross-dependency. Although
> it feels redundant, it seems the proper thing to do would be to include
> writer.hdfs.filesystem in both configs, since both processes have that dep.
> Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
