Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 31 Aug 2017 20:08:00 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13098931.1504200519000.2044.1504210080483@Atlassian.JIRA>
In-Reply-To: <JIRA.13098931.1504200519000@Atlassian.JIRA>
References: <JIRA.13098931.1504200519000@Atlassian.JIRA> <JIRA.13098931.1504200519920@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AMBARI-21866) ATS Applications Do Not Move From
 Active to Done After Upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 31 Aug 2017 20:08:05 -0000


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

Hudson commented on AMBARI-21866:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #98 (See [https://builds.apache.org/job/Ambari-branch-2.6/98/])
AMBARI-21866 - ATS Applications Do Not Move From Active to Done After (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=83ea318234bd5d609b72cb62d3db42d2c9345aaa])
* (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/YARN/configuration/yarn-site.xml


> ATS Applications Do Not Move From Active to Done After Upgrade
> --------------------------------------------------------------
>
>                 Key: AMBARI-21866
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21866
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21866.patch
>
>
> When running Tez jobs, it was noticed that after killing the applications, ATS would never move them from the active directory to the done directory. The YARN folks deep some technical investigation and determined that the reason for this was a combination of ATS 1.0 and 1.5 configurations co-existing after upgrading from BigInsights to HDP.
> The upgrade auto-merge should have taken care of this for us, but it seems that 1 property was missing from the default stack BI 4.2 (even though it gets added on install through the UI).
> {code}
> grep -r --include "*.xml" "yarn.timeline-service.store-class" src/main/resources/stacks/BigInsights
> src/main/resources/stacks/BigInsights/4.0/services/YARN/configuration/yarn-site.xml:    <name>yarn.timeline-service.store-class</name>
> src/main/resources/stacks/BigInsights/4.2.5/services/YARN/configuration/yarn-site.xml:    <name>yarn.timeline-service.store-class</name>
> {code}
> BI 4.2.0 doesn't have this property, which causes the merge to fail. It doesn't inherit it from BI 4.0 either.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)