You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2014/02/12 02:01:08 UTC
[jira] [Updated] (AMBARI-4621) It's possible for host components to
get stuck in installing state.
[ https://issues.apache.org/jira/browse/AMBARI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated AMBARI-4621:
------------------------------------
Description:
*Steps to reproduce:*
# Start 10 node cluster.
# On Step-9 of installer wizard while ongoing install command, Stopped ambari-agent on 9 hosts.
# Hit Retry button.
# Some of the host_components ended up in INSTALL_FAILED state, some in UNKNOWN state and others in INSTALLING state. Host components in INSTALLING state never transitioned to any other state.
*Reason*:
The _ActionScehduler.doWork()_ depends on the HostRoles to timeout before aborting the operation in order to update Host Component status.
This particular issue is caused by a the timing of the change in Host state to UNKNOWN, which happens after processing of in progress stages and before Abort.
was:
*Steps to reproduce:*
# Start 10 node cluster.
# On Step-9 of installer wizard while ongoing install command, Stopped ambari-agent on 9 hosts.
# Hit on Retry button.
# Some of the host_components ended up in INSTALL_FAILED state, some in UNKNOWN state and others in INSTALLING state. Host components in INSTALLING state never transitioned to any other state.
> It's possible for host components to get stuck in installing state.
> -------------------------------------------------------------------
>
> Key: AMBARI-4621
> URL: https://issues.apache.org/jira/browse/AMBARI-4621
> Project: Ambari
> Issue Type: Task
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.5.0
>
>
> *Steps to reproduce:*
> # Start 10 node cluster.
> # On Step-9 of installer wizard while ongoing install command, Stopped ambari-agent on 9 hosts.
> # Hit Retry button.
> # Some of the host_components ended up in INSTALL_FAILED state, some in UNKNOWN state and others in INSTALLING state. Host components in INSTALLING state never transitioned to any other state.
> *Reason*:
> The _ActionScehduler.doWork()_ depends on the HostRoles to timeout before aborting the operation in order to update Host Component status.
> This particular issue is caused by a the timing of the change in Host state to UNKNOWN, which happens after processing of in progress stages and before Abort.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)