[HDFS-8153] Error Message points to wrong parent directory in case of path component name length error

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.2
• Fix Version/s: 2.8.0, 2.7.1, 3.0.0-alpha1
• Component/s: namenode
• Target Version/s: 2.7.1
• Assignee: Anu Engineer
• Reporter: Anu Engineer
• Created: 15/Apr/15 21:06
• Updated: 06/Jan/17 01:30
• Resolved: 17/Apr/15 05:29

Description

If the name component length is greater than the permitted length, the error message points to wrong parent directory for mkdir and touchz.

Here are examples where the parent directory name is in error message. In this example dfs.namenode.fs-limits.max-component-length is set to 19.

hdfs dfs -mkdir /user/hrt_qa/FileNameLength/really_big_name_dir01
mkdir: The maximum path component name limit of really_big_name_dir01 in directory /user/hrt_qa/ is exceeded: limit=19 length=21

The expected value for the directory was /user/hrt_qa/FileNameLength. The same behavior is observed for touchz

hdfs dfs -touchz /user/hrt_qa/FileNameLength/really_big_name_0004
touchz: The maximum path component name limit of really_big_name_0004 in directory /user/hrt_qa/ is exceeded: limit=19 length=20