You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/08/28 15:17:00 UTC

[jira] [Commented] (AMBARI-24550) Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 to 2.7.1.0

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

Hudson commented on AMBARI-24550:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9898 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9898/])
AMBARI-24550. Yarn Timeline Service V2 Reader goes down after Ambari (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=93e177c81a1cc438b80d5eddbbb3afe0549a79ee])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog271.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog271Test.java


> Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 to 2.7.1.0
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-24550
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24550
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.0
>            Reporter: Attila Magyar
>            Assignee: Attila Magyar
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.1
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> STR:
> 1) Install cluster with Ambari2.7.0.0 + HDP-3.0.0.0
> 2) Upgrade Ambari to 2.7.1.0
> Yarn Timeline Service V2 Reader goes down after some time.
> Reason: the placeholders in yarn.timeline-service.reader.webapp.address and yarn.timeline-service.reader.webapp.https.address are no longer replaced by the stack code so these values become empty. In this case the timeline reader will use the default ports which may conflict with   other ports used by other components.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)