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

Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2018/05/14 14:10:00 UTC

[jira] [Resolved] (AMBARI-23493) Decommission Datanode doesn't work

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

Dmytro Sen resolved AMBARI-23493.
---------------------------------
    Resolution: Fixed

> Decommission Datanode doesn't work
> ----------------------------------
>
>                 Key: AMBARI-23493
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23493
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> On an Ambari270 cluster, try to decommission a datanode.
> You could see bgop is triggerred and shows as sucsessful.
> But Datanode seems to be still in started state and Decommission op is still available in dropdown.
> The issue is caused by recent perf changes.



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