You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Jerome Boulon (JIRA)" <ji...@apache.org> on 2016/03/22 04:01:25 UTC

[jira] [Updated] (CHUKWA-209) All M/R should get their configuration from ChukwaConfiguration

     [ https://issues.apache.org/jira/browse/CHUKWA-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerome Boulon updated CHUKWA-209:
---------------------------------
    Assignee:     (was: Jerome Boulon)

> All M/R should get their configuration from ChukwaConfiguration
> ---------------------------------------------------------------
>
>                 Key: CHUKWA-209
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-209
>             Project: Chukwa
>          Issue Type: Bug
>            Reporter: Jerome Boulon
>
> Most of M/R are creating configuration on their own, instead they should use a centralized configuration coming from ChukwaConfiguration.
> Add new static methods to ChukwaConfiguration in order to get configuration for the agent side or the backend side.
> This should simplify the configuration management and avoid several the creation of several instances of ChukwaCnfiguration with the same content.
> Ideally ChukwaConfiguration should have a private constructor to enforce the usage of a single configuration per process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)