ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9669) Spark components stuck in UPGRADING state
Date Mon, 16 Feb 2015 21:13:11 GMT

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

Hudson commented on AMBARI-9669:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #1784 (See [https://builds.apache.org/job/Ambari-trunk-Commit/1784/])
AMBARI-9669. Spark components stuck in UPGRADING state (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fd07a3e3446767588b1427d600151684e9798023)
* ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/params.py


> Spark components stuck in UPGRADING state
> -----------------------------------------
>
>                 Key: AMBARI-9669
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9669
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.0.0
>
>
> Stuck while testing rolling Upgrade ( 2.2.2.0-2355 --> 2.2.2.0-2357 ) on a 3 node
cluster. Steps followed :
> # Setup NameNode HA successfully
> # Added a new version and we were able to get the HDP 2.2.2.0-2357 installed successfully
> # Checked on each node and we had 2.2.2.0-2357 in /usr/hdp on all three nodes. So installation
was successful.
> # However the UI just hangs ( with loading sign ) at the next step ( where we have to
actually click "Upgrade" to make the upgrade process start )
> Note: Spark changes are ruled out, because the upgrade process was yet not started. The
screen hangs at the install of newer version of hdp itself.
> ----
> Tried again  (2.2.2.0-2361 --> 2.2.2.0-2362) on another 3 node cluster and got the
same error.



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

Mime
View raw message