hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ari Rabkin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7573) hadoop should log configuration reads
Date Fri, 02 Sep 2011 18:43:16 GMT

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

Ari Rabkin updated HADOOP-7573:
-------------------------------

    Attachment: HADOOP-7573.patch

Revised as per Todd. Priority is trace, and there's a commented-out line in log4j.properties
to enable this. 

I notice that hardly anything else in Configuration is logged as debug, and nothing else is
trace. Perhaps ditch the second Logger, and just log through base logger? 

I'd rather have these messages ON by default: Hadoop should be easy to debug and troubleshoot
out of the box. But apparently this isn't the consensus view?

> hadoop should log configuration reads
> -------------------------------------
>
>                 Key: HADOOP-7573
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7573
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 0.20.203.0
>            Reporter: Ari Rabkin
>            Assignee: Ari Rabkin
>            Priority: Minor
>             Fix For: 0.20.206.0
>
>         Attachments: HADOOP-7573.patch, HADOOP-7573.patch, HADOOP-7573.patch, HADOOP-7573.patch
>
>
> For debugging, it would often be valuable to know which configuration options ever got
read out of the Configuration into the rest of the program -- an unread option didn't cause
a problem. This patch logs the first time each option is read.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message