[
https://issues.apache.org/jira/browse/AMBARI-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-21621:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk and branch-2.5
> Do not call refreshnodes command after deleting a slave
> -------------------------------------------------------
>
> Key: AMBARI-21621
> URL: https://issues.apache.org/jira/browse/AMBARI-21621
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21621_2.patch, AMBARI-21621_3.patch,
> AMBARI-21621.patch
>
>
> If DN is deleted the hostname is removed from exclude file and refreshnodes
> command is called. If those actions are not followed by NN restart, the
> deleted DN will be shown as DEAD on NN UI.
> The slave should be removed by NN from the UI, but Ambari should not call
> refreshnodes command on deletion to ensure slave is in "decommissioned and
> dead" state, not "dead"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
