[
https://issues.apache.org/jira/browse/AMBARI-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112646#comment-16112646
]
Hudson commented on AMBARI-21621:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7841 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7841/])
AMBARI-21621 Do not call refreshnodes command after deleting a slave (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4a122a220d28da86da7cafdf89d00b5c09ae4193])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
* (edit)
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_windows.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_windows.py
> 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)
