[HDFS-14164] Namenode should not be started if safemode threshold is out of boundary

• Type: Bug
• Status: Patch Available
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.7.3, 3.1.1
• Component/s: namenode
• Labels: patch

Environment

#apache hadoop-3.1.1

• Flags: Patch
• Assignee: Karthik Palanisamy
• Reporter: Karthik Palanisamy
• Created: 21/Dec/18 02:39
• Updated: 20/Mar/19 00:47

Description

Mistakenly,  User has configured safemode threshold(dfs.namenode.safemode.threshold-pct) to 090 instead of 0.90. Due to this change,  UI has the incorrect summary and it never turns to be out of safemode until manual intervention. Because total block count will never match with an additional block count, which is to be reported.

 I.e

Wrong setting: dfs.namenode.safemode.threshold-pct=090

Summary:

Safe mode is ON. The reported blocks 0 needs additional 360 blocks to reach the threshold 90.0000 of total blocks 4. The number of live datanodes 3 has reached the minimum number 0. Safe mode will be turned off automatically once the thresholds have been reached.

10 files and directories, 4 blocks (4 replicated blocks, 0 erasure coded block groups) = 14 total filesystem object(s).

 

Issue Links

• relates to: HDFS-3325 When configuring "dfs.namenode.safemode.threshold-pct" to a value greater or equal to 1 there is mismatch in the UI report