[
https://issues.apache.org/jira/browse/AMBARI-10495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497812#comment-14497812
]
Hari Sekhon commented on AMBARI-10495:
--------------------------------------
Thanks that workaround works. I had looked the db before but didn't find the
state, now I've reset that manually in the DB I've managed to trigger a new run
of the stack installation.
Would it be possible to add self-timeouts to all Ambari actions such as this to
just reset their state if it hasn't completed after a set amount of time had
passed? (this was stuck like this for days)
> Ambari 2.0 Stack deployment stuck after failure to deploy HDP 2.2.4 stack
> -------------------------------------------------------------------------
>
> Key: AMBARI-10495
> URL: https://issues.apache.org/jira/browse/AMBARI-10495
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
> Affects Versions: 2.0.0
> Environment: HDP 2.2.0 => HDP 2.2.4
> Reporter: Hari Sekhon
> Priority: Blocker
> Attachments: Ambari_2_installed_4_failed.png,
> Ambari_stuck_installing_stack.png
>
>
> When trying to install the HDP 2.2.4.0 stack in Ambari 2.0 if it fails for
> any reason (eg. AMBARI-10494) then the failing nodes are marked as failed but
> the stack stays in the "installing" state indefinitely, even after restarting
> ambari-server and all agents (I even did this simulatenously in parallel to
> make sure one wasn't restoring the state to the other).
> I've attached screenshots and the log file from one of the failed nodes to
> show the full output.
> This is completely blocking deployment of the new HDP 2.2.4 stack to upgrade
> the cluster.
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
