hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3483) hdfs fsck doesn't run with ViewFS path
Date Fri, 01 Jun 2012 19:18:23 GMT

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

Daryn Sharp commented on HDFS-3483:
-----------------------------------

As you can tell by the "hdfs" command name, the commands like fsck & dfsadmin are designed
specifically for hdfs.  With viewfs, it's not possible to know the real fs for a path so the
only option is to directly run the commands on the real hdfs filesystem.  That's an "easy"
answer for fsck, but not for setQuota.  Having to know the mount point's fs to run quota commands
shatters the transparency of viewfs.

In either command's case, the required apis are only in {{DistributedFileSystem}}.  If they
were defined by {{FileSystem}} to be a no-op or exception, then perhaps there could be a general
"hadoop fs -setQuota" or "hadoop fsck".  {{ViewFileSystem}} could implement the commands to
delegate thru to the mounted fs.


                
> hdfs fsck doesn't run with ViewFS path
> --------------------------------------
>
>                 Key: HDFS-3483
>                 URL: https://issues.apache.org/jira/browse/HDFS-3483
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Stephen Chu
>         Attachments: core-site.xml, hdfs-site.xml
>
>
> I'm running a HA + secure + federated cluster.
> When I run "hdfs fsck /nameservices/ha-nn-uri/", I see the following:
> bash-3.2$ hdfs fsck /nameservices/ha-nn-uri/
> FileSystem is viewfs://oracle/
> DFSck exiting.
> Any path I enter will return the same message.
> Attached are my core-site.xml and hdfs-site.xml.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message