[
https://issues.apache.org/jira/browse/CHUKWA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700951#action_12700951
]
Mac Yang commented on CHUKWA-162:
---------------------------------
And that's why it's not a blocker.
It's current forcing all these config files to be meshed together and that
seems like a bad design.
* hadoop-site.xml
* chukwa-agent-conf.xml
* chukwa-collector-conf.xml
* chukwa-demux-conf.xml
What happens when the map reduced based aggregation becomes available? I don't
think it makes sense to limit that to use the same settings as the demux jobs.
> 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.
