[
https://issues.apache.org/jira/browse/AMBARI-25232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned AMBARI-25232:
-------------------------------------
Assignee: Viraj Jasani
Affects Version/s: 2.7.4
2.6.2
Description:
During Decommission workflow, even though we change include/exclude files and
apply refreshNodes command, sometimes NameNode UI still shows DataNodes in old
status.
However, if we include calling configure() for NameNode after refreshNode,
NameNode correctly detects decommissioned DataNodes.
Component/s: ambari-server
Issue Type: Bug (was: Task)
Summary: Decommission workflow to refresh HDFS client (was:
Decommission should configure )
> Decommission workflow to refresh HDFS client
> --------------------------------------------
>
> Key: AMBARI-25232
> URL: https://issues.apache.org/jira/browse/AMBARI-25232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.2, 2.7.4
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
>
> During Decommission workflow, even though we change include/exclude files and
> apply refreshNodes command, sometimes NameNode UI still shows DataNodes in
> old status.
> However, if we include calling configure() for NameNode after refreshNode,
> NameNode correctly detects decommissioned DataNodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)