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/06/12 14:46:00 UTC
[jira] [Commented] (AMBARI-24078) Components Added During Upgrade
Are Not Scheduled for Restart
[ https://issues.apache.org/jira/browse/AMBARI-24078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509706#comment-16509706 ]
Hudson commented on AMBARI-24078:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9440 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9440/])
[AMBARI-24078] Components Added During Upgrade Are Not Scheduled for (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=709b43baacb9df32268d586f3c8682e7215141cf])
* (add) ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/upgrade_test_add_component.xml
* (edit) ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java
> Components Added During Upgrade Are Not Scheduled for Restart
> -------------------------------------------------------------
>
> Key: AMBARI-24078
> URL: https://issues.apache.org/jira/browse/AMBARI-24078
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> During an upgrade, if a component is automatically added that is already a part of the cluster, it's not scheduled for restart.
>
> STR:
> * Install a cluster with ZK, HDFS, Hive, Spark
> * Make sure not to put Hive Client on every machine
> * During an upgrade, Hive Client is automatically added, but the new components are not scheduled for restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)