[
https://issues.apache.org/jira/browse/AMBARI-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated AMBARI-12308:
---------------------------------
Attachment: ambari-server.log
Ambari_incorrect_last_node_warning.png
> Incorrect warning last node / data loss when trying to remove decommissioned
> data nodes
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-12308
> URL: https://issues.apache.org/jira/browse/AMBARI-12308
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
> Affects Versions: 2.0.0
> Environment: HDP 2.2
> Reporter: Hari Sekhon
> Attachments: Ambari_incorrect_last_node_warning.png, ambari-server.log
>
>
> After the scenario in AMBARI-12307, the two other decommissioned nodes that I
> was trying to remove each give an incorrect warning that this node is the
> last datanode, last of each type of client node that it contains and that
> data loss may result from it's removal.
> This is not true since there are several other nodes, there are no masters on
> either of these nodes and the fact they are fully decommissioned by the
> NameNode means there are no live blocks.
> Needless to say though I'm not removing these nodes as the then it's on my
> head for ignoring this warning even though I'm certain it's wrong.
> The Ambari server was restarted about an hour ago and this state is still
> wrong.
> I'm attaching a screenshot and the ambari-server log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
