[
https://issues.apache.org/jira/browse/HADOOP-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097711#comment-13097711
]
Chris Douglas commented on HADOOP-7573:
---------------------------------------
I'm \-0 on the patch. I have never wished for this hook, but it's out of the
way and I won't block it if another's experience is otherwise.
bq. 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?
Without presuming to speak for Todd, I think the consensus view is that this
change effects significantly more noise than signal. All accurate debug output
is helpful for troubleshooting, but reasonable people will differ in their
tolerance for spurious messages.
> 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
