hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7573) hadoop should log configuration reads
Date Fri, 08 May 2015 23:02:02 GMT

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

Allen Wittenauer updated HADOOP-7573:
          Resolution: Won't Fix
    Target Version/s: 2.7.0, 1.3.0, 2.8.0  (was: 1.3.0, 2.7.0, 2.8.0)
              Status: Resolved  (was: Patch Available)

OK, after a lot of discussion around here, getting multiple inputs, etc, the consensus is
to close this as won't fix.  It would be much more valuable with a source associated with
the read, but for the most part the modern Hadoop stack is pretty good about showing what
configs are actually in play.

> 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:
>            Reporter: Ari Rabkin
>            Assignee: Ari Rabkin
>            Priority: Minor
>         Attachments: HADOOP-7573.patch, HADOOP-7573.patch, 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 was sent by Atlassian JIRA

View raw message