[
https://issues.apache.org/jira/browse/AMBARI-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108761#comment-16108761
]
Hadoop QA commented on AMBARI-21621:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12879798/AMBARI-21621.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11907//console
This message is automatically generated.
> 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.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)
