[
https://issues.apache.org/jira/browse/YARN-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182247#comment-14182247
]
Hadoop QA commented on YARN-2703:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676733/YARN-2703.3.patch
against trunk revision 828429d.
{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:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc 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 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The following test timeouts occurred in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.TestDecommTests
org.apache.hadoop.hdfs.TestParallelUnixDomaTests
org.apache.hadoop.hdfs.TestEncryptionZonesWTests
org.apache.hadoop.hdfs.TestClientProtocolForPipelineRecTests
org.apache.hadoop.hdfs.TestPTestsTests
org.apache.hadoop.hdfs.TestGetBTests
org.apache.hadoop.hdfs.TestFileCreTests
org.apache.hadoop.hdfs.TestWriTests
org.apache.hadoop.hdfs.TestSetrepIncrTests
org.apache.hadoop.hdfs.TestRenameWhiTests
org.apache.hadoop.hdfs.TestBlockReaderLocTesTests
org.apache.hadoop.hdfs.TestEncryptionZoneTeTests
org.apache.hadoop.hdfs.web.TestWebHdfsFileSystemContraTesTests
org.apache.hadoop.hdfs.web.TestWebHDFTeTests
org.apache.hadoop.hdfs.web.TestWebHDFSForHTeTests
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5525//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5525//console
This message is automatically generated.
> Add logUploadedTime into LogValue for better display
> ----------------------------------------------------
>
> Key: YARN-2703
> URL: https://issues.apache.org/jira/browse/YARN-2703
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Attachments: YARN-2703.1.patch, YARN-2703.2.patch, YARN-2703.3.patch
>
>
> Right now, the container can upload its logs multiple times. Sometimes,
> containers write different logs into the same log file. After the log
> aggregation, when we query those logs, it will show:
> LogType: stderr
> LogContext:
> LogType: stdout
> LogContext:
> LogType: stderr
> LogContext:
> LogType: stdout
> LogContext:
> The same files could be displayed multiple times. But we can not figure out
> which logs come first. We could add extra loguploadedTime to let users have
> better understanding on the logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
