[
https://issues.apache.org/jira/browse/HADOOP-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089900#comment-13089900
]
Ari Rabkin commented on HADOOP-7573:
------------------------------------
The intended audience for these log messages is neither users nor developers --
it's supporters who are brought in once a problem appears. That means it'll be
experts able to interpret the messages, but who won't have the opportunity to
add debug statements.
Having a separate logger makes sense; I will do that.
The per-instanceness is a problem; thanks for highlighting that. Open to
suggestions here. Is it crazy to make it static? Once-per-program is the
desired functionality. But I'd like to have it on-by-default; assuming once per
program, the volume of messages will be low. And reproducing problems is a
significant source of time and trouble, so getting the right debug info the
first time is important.
> 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
>
>
> 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
