[AMBARI-14030] Datanode shows up prematurely as 'Decomissioned' in Ambari UI while it is 'Decomissioning in Progress' in Namenode UI

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Component/s: 2.1.3
• Assignee: Xi Wang
• Reporter: Xi Wang
• Created: 24/Nov/15 03:12
• Updated: 25/Nov/15 07:15
• Resolved: 24/Nov/15 23:21

Description

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.