Hadoop QA commented on YARN-3269:

{color:green}+1 overall{color}.  Here are the results of testing the latest 
  against trunk revision 1561231.

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {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 

    {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:green}+1 core tests{color}.  The patch passed unit tests in 

Test results: 
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7047//console

This message is automatically generated.

> Yarn.nodemanager.remote-app-log-dir could not be configured to fully 
> qualified path
> -----------------------------------------------------------------------------------
>                 Key: YARN-3269
>                 URL: https://issues.apache.org/jira/browse/YARN-3269
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>         Attachments: YARN-3269.1.patch, YARN-3269.2.patch
> Log aggregation currently is always relative to the default file system, not 
> an arbitrary file system identified by URI. So we can't put an arbitrary 
> fully-qualified URI into yarn.nodemanager.remote-app-log-dir.

This message was sent by Atlassian JIRA

Reply via email to