You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Anu Engineer (JIRA)" <ji...@apache.org> on 2015/04/15 23:07:01 UTC
[jira] [Created] (HDFS-8153) Error Message points to wrong parent
directory in case of path component name length error
Anu Engineer created HDFS-8153:
----------------------------------
Summary: Error Message points to wrong parent directory in case of path component name length error
Key: HDFS-8153
URL: https://issues.apache.org/jira/browse/HDFS-8153
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Affects Versions: 2.5.2
Reporter: Anu Engineer
Assignee: Anu Engineer
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.
{code}
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
{code}
The expected value for the directory was /user/hrt_qa/FileNameLength. The same behavior is observed for touchz
{code}
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
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)