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 2009/04/02 00:34:12 UTC
[jira] Resolved: (CHUKWA-49) Log4JMetricsContext is using the same
logger, logger should be specific to contextName
[ https://issues.apache.org/jira/browse/CHUKWA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerome Boulon resolved CHUKWA-49.
---------------------------------
Resolution: Fixed
This issue has been solved by CHUKWA-12.
>> Logger logger = Logger.getLogger("chukwa.metrics." + contextName);
> Log4JMetricsContext is using the same logger, logger should be specific to contextName
> --------------------------------------------------------------------------------------
>
> Key: CHUKWA-49
> URL: https://issues.apache.org/jira/browse/CHUKWA-49
> Project: Hadoop Chukwa
> Issue Type: Bug
> Reporter: Jerome Boulon
> Assignee: Jerome Boulon
> Priority: Blocker
>
> Since Log4JMetricsContext is using the class as the logger's name, JVM,MAPRED,HDFS, etc will be sent to the same logger.
> Instead the logger should be specific to a context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.