ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14030) Datanode shows up prematurely as 'Decomissioned' in Ambari UI while it is 'Decomissioning in Progress' in Namenode UI
Date Wed, 25 Nov 2015 07:16:11 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026332#comment-15026332
] 

Hudson commented on AMBARI-14030:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #3907 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3907/])
AMBARI-14030. Datanode shows up prematurely as 'Decomissioned' in Ambari (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=aa465686f3959d76254a8a00cfdd832747a602f4])
* ambari-web/app/views/main/host/details/host_component_views/datanode_view.js


> Datanode shows up prematurely as 'Decomissioned' in Ambari UI while it is 'Decomissioning
in Progress' in Namenode UI
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14030
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14030
>             Project: Ambari
>          Issue Type: Bug
>          Components: 2.1.3
>    Affects Versions: 2.1.3
>            Reporter: Xi Wang
>            Assignee: Xi Wang
>            Priority: Critical
>         Attachments: AMBARI-14030.patch
>
>
> PROBLEM:  After decomissioning a datanode through Ambari, datanode shows up prematurely
as 'Decomissioned' in Ambari UI (in datanode host's component page) while it is 'Decomissioning
in Progress' in Namenode UI.  Furthermore, Ambari will let you stop and delete datanode while
it is decomissioning.
> BUSINESS IMPACT:  Could cause concerns for data loss if there is under-replicated data.
> STEPS TO REPRODUCE:  Decomission a datanode through Ambari.  After Ambari's decomission
command completes (add to dfs.exclude, then refresh nodes), go to the datanode host's component
page and check datanode status.  Compare with Namenode UI.
> EXPECTED RESULT:  Datanode should not prematurely say 'Decomissioned' in its host's component
page in Ambari UI.  It should match state in Namenode UI.
> ACTUAL RESULT:  Datanode prematurely listed as 'Decomissioned' in its host's component
page.
> SUPPORT ANALYSIS:  While decomissioning is in progress, Ambari UI should not allow you
to stop the datanode and delete it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message