[ 
https://issues.apache.org/jira/browse/HDFS-11432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969953#comment-15969953
 ] 

Surendra Singh Lilhore commented on HDFS-11432:
-----------------------------------------------

Hi [~brahmareddy],

bq. allowSnapshot: FileSystem viewfs://ClusterX/ is not an HDFS file system

After this patch also still these commands will not work with "viewfs://" path. 
This patch is solving problem only for the fully qualified path with "hdfs" 
schema.
I think we should change the jira description.

> Federation : Support fully qualified path for 
> Quota/Snapshot/cacheadmin/cryptoadmin commands
> --------------------------------------------------------------------------------------------
>
>                 Key: HDFS-11432
>                 URL: https://issues.apache.org/jira/browse/HDFS-11432
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: federation
>            Reporter: Brahma Reddy Battula
>            Assignee: Brahma Reddy Battula
>             Fix For: 3.0.0-alpha3, 2.8.1
>
>         Attachments: HDFS-11432-002.patch, HDFS-11432-003.patch, 
> HDFS-11432-004.patch, HDFS-11432.patch
>
>
> As of now, client needs to change "fs.defaultFS" to connect to specific name 
> service when cluster is federated cluster which will be inconvenient for user.
>  *Snapshot* 
> {noformat}
>  hdfs dfsadmin -allowSnapshot hdfs://hacluster/Dir1/snapdir2
> allowSnapshot: FileSystem viewfs://ClusterX/ is not an HDFS file system
> Usage: hdfs dfsadmin [-allowSnapshot <snapshotDir>]
> {noformat}
>  *Quota* 
> {noformat}
> hdfs dfsadmin -setQuota 10 hdfs://hacluster/Bulkload
> setQuota: FileSystem viewfs://ClusterX/ is not an HDFS file system
> Usage: hdfs dfsadmin [-setQuota <quota> <dirname>...<dirname>]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to