[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607627#comment-13607627 ] Hudson commented on YARN-200: - Integrated in Hadoop-Mapreduce-trunk #1378 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1378/]) YARN-200. yarn log does not output all needed information, and is in a binary format. Contributed by Ravi Prakash (Revision 1458466) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1458466 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/AggregatedLogFormat.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/LogDumper.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/logaggregation/TestLogAggregationService.java > yarn log does not output all needed information, and is in a binary format > -- > > Key: YARN-200 > URL: https://issues.apache.org/jira/browse/YARN-200 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 0.23.5 >Reporter: Robert Joseph Evans >Assignee: Ravi Prakash > Labels: usability > Fix For: 0.23.7, 2.0.5-beta > > Attachments: YARN-200.patch, YARN-200.patch > > > yarn logs does not output attemptid, nodename, or container-id. Missing > these makes it very difficult to look through the logs for failed containers > and tie them back to actual tasks and task attempts. > Also the output currently includes several binary characters. This is OK for > being machine readable, but difficult for being human readable, or even for > using standard tool like grep. > The help message can also be more useful to users -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607571#comment-13607571 ] Hudson commented on YARN-200: - Integrated in Hadoop-Hdfs-trunk #1350 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1350/]) YARN-200. yarn log does not output all needed information, and is in a binary format. Contributed by Ravi Prakash (Revision 1458466) Result = FAILURE jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1458466 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/AggregatedLogFormat.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/LogDumper.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/logaggregation/TestLogAggregationService.java > yarn log does not output all needed information, and is in a binary format > -- > > Key: YARN-200 > URL: https://issues.apache.org/jira/browse/YARN-200 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 0.23.5 >Reporter: Robert Joseph Evans >Assignee: Ravi Prakash > Labels: usability > Fix For: 0.23.7, 2.0.5-beta > > Attachments: YARN-200.patch, YARN-200.patch > > > yarn logs does not output attemptid, nodename, or container-id. Missing > these makes it very difficult to look through the logs for failed containers > and tie them back to actual tasks and task attempts. > Also the output currently includes several binary characters. This is OK for > being machine readable, but difficult for being human readable, or even for > using standard tool like grep. > The help message can also be more useful to users -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607564#comment-13607564 ] Hudson commented on YARN-200: - Integrated in Hadoop-Hdfs-0.23-Build #559 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/559/]) svn merge -c 1458466 FIXES: YARN-200. yarn log does not output all needed information, and is in a binary format. Contributed by Ravi Prakash (Revision 1458474) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1458474 Files : * /hadoop/common/branches/branch-0.23/hadoop-yarn-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/AggregatedLogFormat.java * /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/LogDumper.java * /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/logaggregation/TestLogAggregationService.java > yarn log does not output all needed information, and is in a binary format > -- > > Key: YARN-200 > URL: https://issues.apache.org/jira/browse/YARN-200 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 0.23.5 >Reporter: Robert Joseph Evans >Assignee: Ravi Prakash > Labels: usability > Fix For: 0.23.7, 2.0.5-beta > > Attachments: YARN-200.patch, YARN-200.patch > > > yarn logs does not output attemptid, nodename, or container-id. Missing > these makes it very difficult to look through the logs for failed containers > and tie them back to actual tasks and task attempts. > Also the output currently includes several binary characters. This is OK for > being machine readable, but difficult for being human readable, or even for > using standard tool like grep. > The help message can also be more useful to users -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607496#comment-13607496 ] Hudson commented on YARN-200: - Integrated in Hadoop-Yarn-trunk #161 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/161/]) YARN-200. yarn log does not output all needed information, and is in a binary format. Contributed by Ravi Prakash (Revision 1458466) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1458466 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/AggregatedLogFormat.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/LogDumper.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/logaggregation/TestLogAggregationService.java > yarn log does not output all needed information, and is in a binary format > -- > > Key: YARN-200 > URL: https://issues.apache.org/jira/browse/YARN-200 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 0.23.5 >Reporter: Robert Joseph Evans >Assignee: Ravi Prakash > Labels: usability > Fix For: 0.23.7, 2.0.5-beta > > Attachments: YARN-200.patch, YARN-200.patch > > > yarn logs does not output attemptid, nodename, or container-id. Missing > these makes it very difficult to look through the logs for failed containers > and tie them back to actual tasks and task attempts. > Also the output currently includes several binary characters. This is OK for > being machine readable, but difficult for being human readable, or even for > using standard tool like grep. > The help message can also be more useful to users -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606697#comment-13606697 ] Hudson commented on YARN-200: - Integrated in Hadoop-trunk-Commit #3492 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3492/]) YARN-200. yarn log does not output all needed information, and is in a binary format. Contributed by Ravi Prakash (Revision 1458466) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1458466 Files : * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/AggregatedLogFormat.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/LogDumper.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/logaggregation/TestLogAggregationService.java > yarn log does not output all needed information, and is in a binary format > -- > > Key: YARN-200 > URL: https://issues.apache.org/jira/browse/YARN-200 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 0.23.5 >Reporter: Robert Joseph Evans >Assignee: Ravi Prakash > Labels: usability > Attachments: YARN-200.patch, YARN-200.patch > > > yarn logs does not output attemptid, nodename, or container-id. Missing > these makes it very difficult to look through the logs for failed containers > and tie them back to actual tasks and task attempts. > Also the output currently includes several binary characters. This is OK for > being machine readable, but difficult for being human readable, or even for > using standard tool like grep. > The help message can also be more useful to users -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606686#comment-13606686 ] Jason Lowe commented on YARN-200: - The 'nodename_port' string in the usage should be 'nodename:port', otherwise +1. I'll make the one-character fix when I commit. > yarn log does not output all needed information, and is in a binary format > -- > > Key: YARN-200 > URL: https://issues.apache.org/jira/browse/YARN-200 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 0.23.5 >Reporter: Robert Joseph Evans >Assignee: Ravi Prakash > Labels: usability > Attachments: YARN-200.patch, YARN-200.patch > > > yarn logs does not output attemptid, nodename, or container-id. Missing > these makes it very difficult to look through the logs for failed containers > and tie them back to actual tasks and task attempts. > Also the output currently includes several binary characters. This is OK for > being machine readable, but difficult for being human readable, or even for > using standard tool like grep. > The help message can also be more useful to users -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606564#comment-13606564 ] Ravi Prakash commented on YARN-200: --- Jason suggested I should check if unicode characters were displayed properly too. I did and they are. > yarn log does not output all needed information, and is in a binary format > -- > > Key: YARN-200 > URL: https://issues.apache.org/jira/browse/YARN-200 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 0.23.5 >Reporter: Robert Joseph Evans >Assignee: Ravi Prakash > Labels: usability > Attachments: YARN-200.patch, YARN-200.patch > > > yarn logs does not output attemptid, nodename, or container-id. Missing > these makes it very difficult to look through the logs for failed containers > and tie them back to actual tasks and task attempts. > Also the output currently includes several binary characters. This is OK for > being machine readable, but difficult for being human readable, or even for > using standard tool like grep. > The help message can also be more useful to users -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[
https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605608#comment-13605608
]
Hadoop QA commented on YARN-200:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12574206/YARN-200.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 tests included appear to have a timeout.{color}
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/533//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/533//console
This message is automatically generated.
> yarn log does not output all needed information, and is in a binary format
> --
>
> Key: YARN-200
> URL: https://issues.apache.org/jira/browse/YARN-200
> Project: Hadoop YARN
> Issue Type: Sub-task
>Affects Versions: 0.23.5
>Reporter: Robert Joseph Evans
>Assignee: Ravi Prakash
> Labels: usability
> Attachments: YARN-200.patch, YARN-200.patch
>
>
> yarn logs does not output attemptid, nodename, or container-id. Missing
> these makes it very difficult to look through the logs for failed containers
> and tie them back to actual tasks and task attempts.
> Also the output currently includes several binary characters. This is OK for
> being machine readable, but difficult for being human readable, or even for
> using standard tool like grep.
> The help message can also be more useful to users
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[
https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605171#comment-13605171
]
Hadoop QA commented on YARN-200:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12574150/YARN-200.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/529//console
This message is automatically generated.
> yarn log does not output all needed information, and is in a binary format
> --
>
> Key: YARN-200
> URL: https://issues.apache.org/jira/browse/YARN-200
> Project: Hadoop YARN
> Issue Type: Sub-task
>Affects Versions: 0.23.5
>Reporter: Robert Joseph Evans
>Assignee: Ravi Prakash
> Labels: usability
> Attachments: YARN-200.patch
>
>
> yarn logs does not output attemptid, nodename, or container-id. Missing
> these makes it very difficult to look through the logs for failed containers
> and tie them back to actual tasks and task attempts.
> Also the output currently includes several binary characters. This is OK for
> being machine readable, but difficult for being human readable, or even for
> using standard tool like grep.
> The help message can also be more useful to users
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format
[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605166#comment-13605166 ] Ravi Prakash commented on YARN-200: --- All these requests come courtesy Koji! > yarn log does not output all needed information, and is in a binary format > -- > > Key: YARN-200 > URL: https://issues.apache.org/jira/browse/YARN-200 > Project: Hadoop YARN > Issue Type: Sub-task >Affects Versions: 0.23.5 >Reporter: Robert Joseph Evans >Assignee: Ravi Prakash > Labels: usability > Attachments: YARN-200.patch > > > yarn logs does not output attemptid, nodename, or container-id. Missing > these makes it very difficult to look through the logs for failed containers > and tie them back to actual tasks and task attempts. > Also the output currently includes several binary characters. This is OK for > being machine readable, but difficult for being human readable, or even for > using standard tool like grep. > The help message can also be more useful to users -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
