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-12867) Do Not Automatically Abort Stack Repository Installation When A Host Timed Out
Date Tue, 25 Aug 2015 16:13:46 GMT

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

Hudson commented on AMBARI-12867:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #3318 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3318/])
AMBARI-12867 - Do Not Automatically Abort Stack Repository Installation When A Host Timed
Out (jonathanhurley (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bba679959b3edc16db507faeacd84d33167bbcf4)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
* ambari-server/src/main/java/org/apache/ambari/server/Role.java


> Do Not Automatically Abort Stack Repository Installation When A Host Timed Out
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-12867
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12867
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.2
>
>
> On 1000 node RU I had 2.3.0.0-2557 installed with some 20 hosts down with heartbeat lost.
Then I registered 2.3.2.0-2664 and when I proceeded to install, it would always get aborted
with no logs in server or agents. 
> Turns out that whenever we install, we do so in stages containing 100 hosts each. If
any of the host failed or timed out etc., the rest of the stages are aborted. So in this case
the first stage had 1 host timeout, which resulted in that and other stages being aborted.
> I cannot install a version without all hosts being alive. Workaround seems to be to delete
lost hosts from Ambari.



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

Mime
View raw message