You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/06/19 08:55:00 UTC
[jira] [Commented] (AMBARI-25232) Decommission/Recommission
workflow to refresh HDFS client
[ https://issues.apache.org/jira/browse/AMBARI-25232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867403#comment-16867403 ]
Hudson commented on AMBARI-25232:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #531 (See [https://builds.apache.org/job/Ambari-branch-2.7/531/])
[AMBARI-25232] : Refresh NameNode client with Commission/Decommission… (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=fe5344da60bd770d7caf25cfe32f4fe9fbdd0e68])
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
> Decommission/Recommission 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
> Labels: pull-request-available
> Fix For: 2.6.2, 2.7.4
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> During Decommission/Recommission workflow for DataNode, even though we change include/exclude files and apply refreshNodes command, sometimes NameNode UI still shows DataNodes in old status.
> If we run configure action for NameNode hosts, NameNode correctly detects decommissioned/commissioned(live/dead) DataNodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)