hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7573) hadoop should log configuration reads
Date Wed, 14 Sep 2011 09:53:09 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104392#comment-13104392
] 

Steve Loughran commented on HADOOP-7573:
----------------------------------------

One more thing: whatever the outcome, this should not be a substitute for improving error
messages. The user base of Hadoop spreads from people who set their clusters up in a private
/16 subnet with caching DNS servers on every machine to prevent DNS overload and datacentre-grade
CM tooling, all the way down to people with laptop who don't know what a TCP Connection Refused
error means. 

> 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