You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Viraj Jasani (JIRA)" <ji...@apache.org> on 2019/04/06 20:03:00 UTC

[jira] [Updated] (AMBARI-25232) Decommission workflow to refresh HDFS client

     [ https://issues.apache.org/jira/browse/AMBARI-25232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viraj Jasani updated AMBARI-25232:
----------------------------------
    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 run configure action for NameNode hosts, NameNode correctly detects decommissioned DataNodes.

  was:
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.


> 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 run configure action for NameNode hosts, NameNode correctly detects decommissioned DataNodes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)