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

Hadoop QA commented on AMBARI-16026:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12800081/AMBARI-16026.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:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6595//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6595//console

This message is automatically generated.

> YARN ATS Should Advertise a Version
> -----------------------------------
>
>                 Key: AMBARI-16026
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16026
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16026.patch
>
>
> In YARN's {{metainfo.xml}}, ATS does not have a {{versionAdvertised}} 
> element. As a result, the absence of this element causes Ambari to think that 
> YARN is not part of the {{hdp-select}} logic and we will never validate that 
> it is reporting the correct version on startup.
> However, YARN ATS does have a version and an entry in {{hdp-select}}:
> {code}
>     if params.version and check_stack_feature(StackFeature.ROLLING_UPGRADE, 
> params.version):
>       conf_select.select(params.stack_name, "hadoop", params.version)
>       stack_select.select("hadoop-yarn-timelineserver", params.version)
> {code}
> {code}
> [root@c6401 ~]# cat /usr/bin/hdp-select | grep "timeline"
>            "hadoop-yarn-timelineserver": "hadoop-yarn",
>                          "hadoop-yarn-timelineserver"],
> {code}
> This actually causes the ATS component to say it has a {{VERSION_MISMATCH}} 
> since upgrading HDP changes it's version when we were not expecting it to:
> {code}
> YARN_CLIENT 2.4.2.0-39 COMPLETE       UNKNOWN
> APP_TIMELINE_SERVER   2.4.2.0-39 VERSION_MISMATCH     UNSECURED
> ZOOKEEPER_SERVER       2.4.2.0-39 COMPLETE    UNSECURED
> {code}



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

Reply via email to