You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Jianfei Jiang (JIRA)" <ji...@apache.org> on 2018/04/05 02:27:00 UTC
[jira] [Created] (HDFS-13401) Different behavior in mkdir when the
target folder of mount table is uncreated
Jianfei Jiang created HDFS-13401:
------------------------------------
Summary: Different behavior in mkdir when the target folder of mount table is uncreated
Key: HDFS-13401
URL: https://issues.apache.org/jira/browse/HDFS-13401
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Jianfei Jiang
Assignee: Jianfei Jiang
In federation cases, if we have a config like below:
<property>
<name>fs.viewfs.mounttable.ClusterX.link./foo</name>
<value>hdfs://nn2-clusterx.example.com:8020/footarget</value>
</property>
When the folder hdfs://nn2-clusterx.example.com:8020/projects/footarget is not actually exist, the command [[hdfs dfs ls /]] can still see the folder, but the folder is not actually exist. then we try to use mkdir command to create the viewfs folder [[hdfs dfs mkdir /foo]], the return code is true, but the folder is not created. However, when we use [[hdfs dfs mkdir -p /foo/xxx]] which have a deeper location to create folder, the folder is successfully created. The results in these two cases may be ambigiuous.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org