You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2014/04/30 12:39:14 UTC

[jira] [Assigned] (AMBARI-5589) Cannot start NodeManager after decommissioning, deleting, and then adding it back

     [ https://issues.apache.org/jira/browse/AMBARI-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lysnichenko reassigned AMBARI-5589:
------------------------------------------

    Assignee: Dmitry Lysnichenko

> Cannot start NodeManager after decommissioning, deleting, and then adding it back
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-5589
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5589
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.6.0
>            Reporter: Dmytro Shkvyra
>            Assignee: Dmitry Lysnichenko
>             Fix For: 1.6.1
>
>
> I decommissioned a NodeManager on a host, and then deleted it.
> Then I added NodeManager back to the same host.
> NodeManager will no longer start on this host, because from the ResourceManager's perspective, this host is still in the exclude list.



--
This message was sent by Atlassian JIRA
(v6.2#6252)