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

Posted to dev@ambari.apache.org by "Dmytro Shkvyra (JIRA)" <ji...@apache.org> on 2014/04/28 13:36:14 UTC

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

Dmytro Shkvyra created AMBARI-5589:
--------------------------------------

             Summary: 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
             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)