[
https://issues.apache.org/jira/browse/AMBARI-23096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23096:
------------------------------------
Labels: pull-request-available (was: )
> Ambari needs to call refreshNodes after deleting a host that was running a
> datanode
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-23096
> URL: https://issues.apache.org/jira/browse/AMBARI-23096
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.1
> Environment: Ambari 2.6.1
> Reporter: Sanjeev
> Priority: Minor
> Labels: pull-request-available
>
> Currently when a host(that was running a datanode) is completely deleted from
> the cluster, refreshnode on HDFS is not called and thus the the deleted
> datanode continues to show up in the HDFS NN UI. The UI is refreshed when we
> explicitly run refreshNodes.
> Ambari already has the information which slave components a given host is
> running, if a host being deleted is one among the hosts that was running a
> datanode, then deleting it should trigger refreshNodes as part of the delete
> workflow
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
