Details
-
Improvement
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Motivation:
As of now, clients need to specify a nameservice when a cluster is federated, otherwise, the exception is fired:
hdfs dfsadmin -setQuota 10 viewfs://vfs-root/user/uname setQuota: FileSystem viewfs://vfs-root/ is not an HDFS file system # with fs.defaultFS = viewfs://vfs-root/ hdfs dfsadmin -setQuota 10 vfs-root/user/uname setQuota: FileSystem viewfs://vfs-root/ is not an HDFS file system # works fine thanks to https://issues.apache.org/jira/browse/HDFS-11432 hdfs dfsadmin -setQuota 10 hdfs://users-fs/user/uname
This creates inconvenience, inability to rely on fs.defaultFS and forces to create client-side mappings for management scripts
Implementation:
PathData that is passed to commands should be resolved to its actual FileSystem
Result:
ViewFS will be resolved to the actual HDFS file system
Attachments
Attachments
Issue Links
- relates to
-
HDFS-12929 There is error message when hdfs dfsadmin is run against a ViewFS config
- Resolved