Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.0-alpha1
    • Component/s: documentation
    • Labels:
      None

      Description

      a. Execute the command
      ./yarn daemonlog -setlevel xx.xx.xx.xxx:45020 ResourceManager DEBUG
      b. It is not reflecting in process logs even after performing client level operations
      c. Log level is not changed.

      1. CommandsManual.html
        36 kB
        Naganarasimha G R
      2. HADOOP-11575.20150213-1.patch
        5 kB
        Naganarasimha G R
      3. HADOOP-11575.20150213-2.patch
        5 kB
        Naganarasimha G R
      4. HADOOP-11575.20150214-1.patch
        6 kB
        Naganarasimha G R
      5. YarnCommands.html
        35 kB
        Naganarasimha G R

        Issue Links

          Activity

          Hide
          brahmareddy Brahma Reddy Battula added a comment -

          Seems to be this problem can be there in HDFS also,,, Anyway this we need to handle in Hadoop-Common,,can anyone move to hadoop-common( I can't Move)?

          Show
          brahmareddy Brahma Reddy Battula added a comment - Seems to be this problem can be there in HDFS also,,, Anyway this we need to handle in Hadoop-Common,,can anyone move to hadoop-common( I can't Move)?
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Hi Jagadesh Kiran N & Brahma Reddy Battula
          I feel this is not a issue, as the usage of the command is to pass the Log name for example
          /yarn daemonlog -setlevel xx.xx.xx.xxx:45020 org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl DEBUG

          After running the above command you can run a yarn app and check the RM logs to find the debug logs for org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.
          If its working then will close this issue.

          Show
          Naganarasimha Naganarasimha G R added a comment - Hi Jagadesh Kiran N & Brahma Reddy Battula I feel this is not a issue, as the usage of the command is to pass the Log name for example /yarn daemonlog -setlevel xx.xx.xx.xxx:45020 org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl DEBUG After running the above command you can run a yarn app and check the RM logs to find the debug logs for org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl. If its working then will close this issue.
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Or as part of this jira we can do the following :

          1. update the usage as

            Usage: General options are:
            [-getlevel <host:httpPort> <log name>]
            [-setlevel <host:httpPort> <log name> <level>]

          2. update the documentation with an example of using this command
          3. level param currently takes only case sensitive but i think we should support case insensitive value too
          Show
          Naganarasimha Naganarasimha G R added a comment - Or as part of this jira we can do the following : update the usage as Usage: General options are: [-getlevel <host:httpPort> <log name>] [-setlevel <host:httpPort> <log name> <level>] update the documentation with an example of using this command level param currently takes only case sensitive but i think we should support case insensitive value too
          Hide
          aw Allen Wittenauer added a comment -

          we should support case insensitive value too

          These levels are defined by log4j and defined as uppercase everywhere in both code and config. Making it mixed case here means supporting mixed case everywhere...

          But otherwise, yes, I agree this sounds like a documentation issue more than a bug. I'll move this to HADOOP.

          Show
          aw Allen Wittenauer added a comment - we should support case insensitive value too These levels are defined by log4j and defined as uppercase everywhere in both code and config. Making it mixed case here means supporting mixed case everywhere... But otherwise, yes, I agree this sounds like a documentation issue more than a bug. I'll move this to HADOOP.
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Hi Allen Wittenauer,
          Thanks for moving but i had few queries:

          1. whether we can update document for YARN and Hadoop common in the same jira as daemon log is documented separately for Hadoop and YARN,
          2. I feel daemonlog usage can be updated as i mentioned earlier, please provide your opinion on this

            Usage: General options are:
            [-getlevel <host:httpPort> <log name>]
            [-setlevel <host:httpPort> <log name> <level>]

          3. These levels are defined by log4j and defined as uppercase everywhere in both code and config. Making it mixed case here means supporting mixed case everywhere...
            ok, I mentioned this because, its failing at the validation done @ the servlet level and Level.toLevel(string) takes care of appropriate case conversions.

            if (!level.equals(org.apache.log4j.Level.toLevel(level).toString()))

            Unknown macro: { out.println(MARKER + "Bad level }

            else {

          Show
          Naganarasimha Naganarasimha G R added a comment - Hi Allen Wittenauer , Thanks for moving but i had few queries: whether we can update document for YARN and Hadoop common in the same jira as daemon log is documented separately for Hadoop and YARN , I feel daemonlog usage can be updated as i mentioned earlier, please provide your opinion on this Usage: General options are: [-getlevel <host:httpPort> <log name>] [-setlevel <host:httpPort> <log name> <level>] These levels are defined by log4j and defined as uppercase everywhere in both code and config. Making it mixed case here means supporting mixed case everywhere... ok, I mentioned this because, its failing at the validation done @ the servlet level and Level.toLevel(string) takes care of appropriate case conversions. if (!level.equals(org.apache.log4j.Level.toLevel(level).toString())) Unknown macro: { out.println(MARKER + "Bad level } else {
          Hide
          brahmareddy Brahma Reddy Battula added a comment -

          ouch,there is a jira for this improvement .( This is turned to HADOOP-10909.., will try to duplicate HADOOP-10909)..

          Show
          brahmareddy Brahma Reddy Battula added a comment - ouch,there is a jira for this improvement .( This is turned to HADOOP-10909 .., will try to duplicate HADOOP-10909 )..
          Hide
          aw Allen Wittenauer added a comment -

          whether we can update document for YARN and Hadoop common in the same jira

          Go for it.

          I feel daemonlog usage can be updated

          General options are:

          Not a fan of this verbage. I prefer man page style where it is mainly:

          Usage:
             xyz daemonlog optionset1
             xyz daemonlog optionset2
          

          Level.toLevel(string) takes care of appropriate case conversions

          a) If a user defines a custom level, what happens?
          b) What if there is more than just case conversion happening, especially in a i18n capacity?

          Show
          aw Allen Wittenauer added a comment - whether we can update document for YARN and Hadoop common in the same jira Go for it. I feel daemonlog usage can be updated General options are: Not a fan of this verbage. I prefer man page style where it is mainly: Usage: xyz daemonlog optionset1 xyz daemonlog optionset2 Level.toLevel(string) takes care of appropriate case conversions a) If a user defines a custom level, what happens? b) What if there is more than just case conversion happening, especially in a i18n capacity?
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Not a fan of this verbage. I prefer man page style where it is mainly:

          May be i dint convey it correctly, At present {{-getlevel <host:httpPort> <name> . }} is getting displayed in CLI as usage and was planning to do it as {{-getlevel <host:httpPort> <log name> . }}

          And for documentation will update it at the earliest and share the patch

          a) If a user defines a custom level, what happens?
          b) What if there is more than just case conversion happening, especially in a i18n capacity?

          Well IIUC, org.apache.log4j.Level.toLevel(level) supports for only the default types Log4j supports(ALL,DEBUG,INFO,WARN,ERROR,FATAL,OFF,TRACE) and if none of the string matches then selects DEBUG as default.
          Ok if its for sake of uniformity we can keep it as Upper case itself but earlier thought that it would be easier for user to either give in upper case or lower case.

          Show
          Naganarasimha Naganarasimha G R added a comment - Not a fan of this verbage. I prefer man page style where it is mainly: May be i dint convey it correctly, At present {{-getlevel <host:httpPort> <name> . }} is getting displayed in CLI as usage and was planning to do it as {{-getlevel <host:httpPort> <log name> . }} And for documentation will update it at the earliest and share the patch a) If a user defines a custom level, what happens? b) What if there is more than just case conversion happening, especially in a i18n capacity? Well IIUC, org.apache.log4j.Level.toLevel(level) supports for only the default types Log4j supports(ALL,DEBUG,INFO,WARN,ERROR,FATAL,OFF,TRACE) and if none of the string matches then selects DEBUG as default. Ok if its for sake of uniformity we can keep it as Upper case itself but earlier thought that it would be easier for user to either give in upper case or lower case.
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Hi Allen Wittenauer,
          Please find the patch with modifications in yarn and hadoop docs and few modifications servlet and the CLI usage.
          One thing i was not able to update in CommandsManual.md, was This command internally connects to http://host:httpport/logLevel?log=logname , i wanted to append &level=<level> but mvn site was failing for & character.
          If you are aware how to avoid this text being treated as hyperlink in markdown, please inform.

          Show
          Naganarasimha Naganarasimha G R added a comment - Hi Allen Wittenauer , Please find the patch with modifications in yarn and hadoop docs and few modifications servlet and the CLI usage. One thing i was not able to update in CommandsManual.md, was This command internally connects to http://host:httpport/logLevel?log=logname , i wanted to append &level=<level> but mvn site was failing for & character. If you are aware how to avoid this text being treated as hyperlink in markdown, please inform.
          Hide
          hadoopqa Hadoop QA added a comment -

          +1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12698544/HADOOP-11575.20150213-1.patch
          against trunk revision 74f38d5.

          +1 @author. The patch does not contain any @author tags.

          +0 tests included. The patch appears to be a documentation patch that doesn't require tests.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 core tests. The patch passed unit tests in hadoop-common-project/hadoop-common.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5679//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5679//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12698544/HADOOP-11575.20150213-1.patch against trunk revision 74f38d5. +1 @author . The patch does not contain any @author tags. +0 tests included . The patch appears to be a documentation patch that doesn't require tests. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-common-project/hadoop-common. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5679//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5679//console This message is automatically generated.
          Hide
          wheat9 Haohui Mai added a comment -

          Should we consider deprecating this servlet and provide a REST API instead?

          Show
          wheat9 Haohui Mai added a comment - Should we consider deprecating this servlet and provide a REST API instead?
          Hide
          aw Allen Wittenauer added a comment -

          I think log name is misleading here. Maybe class name would be better? Also:

          If you are aware how to avoid this text being treated as hyperlink in markdown, please inform.

          Back ticks. See Federation.md and search for dfsclusterheatlth.jsp for an example.

          Show
          aw Allen Wittenauer added a comment - I think log name is misleading here. Maybe class name would be better? Also: If you are aware how to avoid this text being treated as hyperlink in markdown, please inform. Back ticks. See Federation.md and search for dfsclusterheatlth.jsp for an example.
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Hi Allen Wittenauer,
          Initially even i was thinking about the same, but in log4j terms they call it as log itself and interface definitions also finally narrow down to {{LogFactory.getLog(String name)}
          Also in some places in the code they have used the log created from one class name is used in other classes also . For instance Log in the Name node class is used in many other classes and one such class being : DatanodeManager.registerDatanode

          NameNode.LOG.info("BLOCK* registerDatanode: " + nodeN);

          Hence kept it as "Log Name" itself

          Back ticks. See Federation.md and search for dfsclusterheatlth.jsp for an example.

          Should we consider deprecating this servlet and provide a REST API instead?

          Show
          Naganarasimha Naganarasimha G R added a comment - Hi Allen Wittenauer , Initially even i was thinking about the same, but in log4j terms they call it as log itself and interface definitions also finally narrow down to {{LogFactory.getLog(String name)} Also in some places in the code they have used the log created from one class name is used in other classes also . For instance Log in the Name node class is used in many other classes and one such class being : DatanodeManager.registerDatanode NameNode.LOG.info("BLOCK* registerDatanode: " + nodeN); Hence kept it as "Log Name" itself Back ticks. See Federation.md and search for dfsclusterheatlth.jsp for an example. Should we consider deprecating this servlet and provide a REST API instead?
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Hi Allen Wittenauer,
          Initially even i was thinking about the same, but in log4j terms they call it as log itself and interface definitions also finally narrow down to LogFactory.getLog(String name)
          Also in some places in the code they have used the log created from one class name is used in other classes also . For instance Log in the NameNode class is used in many other classes and one such class being : DatanodeManager.registerDatanode

          NameNode.LOG.info("BLOCK* registerDatanode: " + nodeN);

          Hence kept it as "Log Name" itself

          Back ticks. See Federation.md and search for dfsclusterheatlth.jsp for an example.

          Thanks for sharing, have updated it in the latest patch

          Hi Haohui Mai,

          Should we consider deprecating this servlet and provide a REST API instead?

          IIUC in this case we need to have a REST mapping in each of the daemon service for getting or setting log level,
          and existing servlet approach seems to be simple approach and if really required
          then would not mind to work on it. Also is it required as part of this jira?

          Also i was thinking about the usability of this daemonlog. It would be really difficult to identify the required classes for debugging and then setting them and reverting them. I was thinking more in the lines of reloading the Log config file.
          so that users can modify the log4j and call a similar servlet which can dynamically reload the log4j config.
          If this Idea is good then will check the feasibility and raise a jira for it

          Show
          Naganarasimha Naganarasimha G R added a comment - Hi Allen Wittenauer, Initially even i was thinking about the same, but in log4j terms they call it as log itself and interface definitions also finally narrow down to LogFactory.getLog(String name) Also in some places in the code they have used the log created from one class name is used in other classes also . For instance Log in the NameNode class is used in many other classes and one such class being : DatanodeManager.registerDatanode NameNode.LOG.info("BLOCK* registerDatanode: " + nodeN); Hence kept it as "Log Name" itself Back ticks. See Federation.md and search for dfsclusterheatlth.jsp for an example. Thanks for sharing, have updated it in the latest patch Hi Haohui Mai , Should we consider deprecating this servlet and provide a REST API instead? IIUC in this case we need to have a REST mapping in each of the daemon service for getting or setting log level, and existing servlet approach seems to be simple approach and if really required then would not mind to work on it. Also is it required as part of this jira? Also i was thinking about the usability of this daemonlog. It would be really difficult to identify the required classes for debugging and then setting them and reverting them. I was thinking more in the lines of reloading the Log config file. so that users can modify the log4j and call a similar servlet which can dynamically reload the log4j config. If this Idea is good then will check the feasibility and raise a jira for it
          Hide
          aw Allen Wittenauer added a comment -

          Hence kept it as "Log Name" itself

          I guess the problem I have with log name is that it indicates that one should be passing a filename and not a class. I think users might get confused. On the flip side, messing with daemonlog should really be considered 'advanced' or 'expert' level controls.

          REST

          Definitely outside the scope of this JIRA. Plus, given that DFS browsing switched to REST and broke all sorts of things that worked fine, I'm very down on converting more stuff to REST given that negative experience.

          It would be really difficult to identify the required classes for debugging and then setting them and reverting them. I was thinking more in the lines of reloading the Log config file.

          The whole point of daemonlog is for expert users to toggle various classes at run time to enable and disable debug mode as necessary. Replacing this with a "re-read the log4j config"-type functionality is over-engineering the problem that this was designed to solve... never mind requiring a configuration file change that might conflict with whatever configuration management tools are in place. Re-reading log4j is much better suited for any of the various reload/reconfig/refresh daemon configuration-JIRAs/functionality out there.

          Show
          aw Allen Wittenauer added a comment - Hence kept it as "Log Name" itself I guess the problem I have with log name is that it indicates that one should be passing a filename and not a class. I think users might get confused. On the flip side, messing with daemonlog should really be considered 'advanced' or 'expert' level controls. REST Definitely outside the scope of this JIRA. Plus, given that DFS browsing switched to REST and broke all sorts of things that worked fine, I'm very down on converting more stuff to REST given that negative experience. It would be really difficult to identify the required classes for debugging and then setting them and reverting them. I was thinking more in the lines of reloading the Log config file. The whole point of daemonlog is for expert users to toggle various classes at run time to enable and disable debug mode as necessary. Replacing this with a "re-read the log4j config"-type functionality is over-engineering the problem that this was designed to solve... never mind requiring a configuration file change that might conflict with whatever configuration management tools are in place. Re-reading log4j is much better suited for any of the various reload/reconfig/refresh daemon configuration-JIRAs/functionality out there.
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          I guess the problem I have with log name is that it indicates that one should be passing a filename and not a class. I think users might get confused. On the flip side, messing with daemonlog should really be considered 'advanced' or 'expert' level controls.

          So to conclude shall change it in all places to "Class Name" ?

          Re-reading log4j is much better suited for any of the various reload/reconfig/refresh daemon configuration-JIRAs/functionality out there.

          Ok.

          Show
          Naganarasimha Naganarasimha G R added a comment - I guess the problem I have with log name is that it indicates that one should be passing a filename and not a class. I think users might get confused. On the flip side, messing with daemonlog should really be considered 'advanced' or 'expert' level controls. So to conclude shall change it in all places to "Class Name" ? Re-reading log4j is much better suited for any of the various reload/reconfig/refresh daemon configuration-JIRAs/functionality out there. Ok.
          Hide
          hadoopqa Hadoop QA added a comment -

          +1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12698774/HADOOP-11575.20150213-2.patch
          against trunk revision ba3c80a.

          +1 @author. The patch does not contain any @author tags.

          +0 tests included. The patch appears to be a documentation patch that doesn't require tests.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 core tests. The patch passed unit tests in hadoop-common-project/hadoop-common.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5685//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5685//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12698774/HADOOP-11575.20150213-2.patch against trunk revision ba3c80a. +1 @author . The patch does not contain any @author tags. +0 tests included . The patch appears to be a documentation patch that doesn't require tests. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-common-project/hadoop-common. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5685//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5685//console This message is automatically generated.
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Hi Allen Wittenauer,
          Please find the attached patch with log name changed to class name where ever applicable

          Show
          Naganarasimha Naganarasimha G R added a comment - Hi Allen Wittenauer , Please find the attached patch with log name changed to class name where ever applicable
          Hide
          hadoopqa Hadoop QA added a comment -

          +1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12698908/HADOOP-11575.20150214-1.patch
          against trunk revision 6804d68.

          +1 @author. The patch does not contain any @author tags.

          +0 tests included. The patch appears to be a documentation patch that doesn't require tests.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 core tests. The patch passed unit tests in hadoop-common-project/hadoop-common.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5697//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5697//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12698908/HADOOP-11575.20150214-1.patch against trunk revision 6804d68. +1 @author . The patch does not contain any @author tags. +0 tests included . The patch appears to be a documentation patch that doesn't require tests. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-common-project/hadoop-common. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5697//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5697//console This message is automatically generated.
          Hide
          aw Allen Wittenauer added a comment -

          +1 lgtm

          Committing to trunk.

          Thanks!

          Show
          aw Allen Wittenauer added a comment - +1 lgtm Committing to trunk. Thanks!
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-trunk-Commit #7130 (See https://builds.apache.org/job/Hadoop-trunk-Commit/7130/)
          HADOOP-11575. Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075)

          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm
          • hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          • hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          • hadoop-common-project/hadoop-common/CHANGES.txt
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-trunk-Commit #7130 (See https://builds.apache.org/job/Hadoop-trunk-Commit/7130/ ) HADOOP-11575 . Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java hadoop-common-project/hadoop-common/CHANGES.txt
          Hide
          Naganarasimha Naganarasimha G R added a comment -

          Thanks Allen Wittenauer, for reviewing and committing the patch.

          Show
          Naganarasimha Naganarasimha G R added a comment - Thanks Allen Wittenauer , for reviewing and committing the patch.
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Yarn-trunk #842 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/842/)
          HADOOP-11575. Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075)

          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm
          • hadoop-common-project/hadoop-common/CHANGES.txt
          • hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          • hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Yarn-trunk #842 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/842/ ) HADOOP-11575 . Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm hadoop-common-project/hadoop-common/CHANGES.txt hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #108 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/108/)
          HADOOP-11575. Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075)

          • hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm
          • hadoop-common-project/hadoop-common/CHANGES.txt
          • hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #108 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/108/ ) HADOOP-11575 . Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075) hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm hadoop-common-project/hadoop-common/CHANGES.txt hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #99 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/99/)
          HADOOP-11575. Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075)

          • hadoop-common-project/hadoop-common/CHANGES.txt
          • hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm
          • hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #99 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/99/ ) HADOOP-11575 . Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075) hadoop-common-project/hadoop-common/CHANGES.txt hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Hadoop-Hdfs-trunk #2040 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2040/)
          HADOOP-11575. Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075)

          • hadoop-common-project/hadoop-common/CHANGES.txt
          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm
          • hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          • hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-Hdfs-trunk #2040 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2040/ ) HADOOP-11575 . Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075) hadoop-common-project/hadoop-common/CHANGES.txt hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #109 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/109/)
          HADOOP-11575. Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075)

          • hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm
          • hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          • hadoop-common-project/hadoop-common/CHANGES.txt
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #109 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/109/ ) HADOOP-11575 . Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075) hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md hadoop-common-project/hadoop-common/CHANGES.txt
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Mapreduce-trunk #2059 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2059/)
          HADOOP-11575. Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075)

          • hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md
          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm
          • hadoop-common-project/hadoop-common/CHANGES.txt
          • hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk #2059 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2059/ ) HADOOP-11575 . Daemon log documentation is misleading (Naganarasimha G R via aw) (aw: rev 72389c78dba1e2f7727245838180fb51e5241075) hadoop-common-project/hadoop-common/src/site/markdown/CommandsManual.md hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/YarnCommands.apt.vm hadoop-common-project/hadoop-common/CHANGES.txt hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java

            People

            • Assignee:
              Naganarasimha Naganarasimha G R
              Reporter:
              jagadesh.kiran Jagadesh Kiran N
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development