ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-5589) Cannot start NodeManager after decommissioning, deleting, and then adding it back
Date Mon, 24 Nov 2014 17:50:12 GMT

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

Dmitry Lysnichenko resolved AMBARI-5589.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

> 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: ambari-server
>    Affects Versions: 1.6.0
>            Reporter: Dmytro Shkvyra
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.0.0
>
>
> 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.3.4#6332)

Mime
View raw message