[ 
https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139817#comment-14139817
 ] 

Hadoop QA commented on YARN-2565:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12669873/YARN-2565.3.patch
  against trunk revision 20a076b.

    {color:red}-1 @author{color}.  The patch appears to contain  @author tags 
which the Hadoop community has agreed to not allow in code contributions.

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

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5034//console

This message is automatically generated.

> RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting 
> FileSystemApplicationHistoryStore
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2565
>                 URL: https://issues.apache.org/jira/browse/YARN-2565
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, timelineserver
>    Affects Versions: 2.6.0
>         Environment: Secure cluster with ATS (timeline server enabled) and 
> yarn.resourcemanager.system-metrics-publisher.enabled=true
> so that RM can send Application history to Timeline Store
>            Reporter: Karam Singh
>            Assignee: Zhijie Shen
>         Attachments: YARN-2565.1.patch, YARN-2565.2.patch, YARN-2565.3.patch
>
>
> Observed that RM fails to start in Secure mode when GenericeHistoryService is 
> enabled and ResourceManager is set to use Timeline Store



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to