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

Robert Joseph Evans commented on HDFS-3483:
-------------------------------------------

Daryn,

I tend to disagree that we don't want to expose the mapping.  I think it is 
incredibly useful to be able to know what is happening here, and expose it to 
the end user so they can then reason about what they want to have happen.  For 
example doing a mv from one federated namespace to another will either be very 
slow, or it will fail, I don't remember which it is right now. In either case 
it would be good to expose the mounting to both the end user, and also 
programatically so that appropriate steps can be taken in those situations.  
Even if the step is just to call up ops and complain that they have the 
namespaces all wrong for what they want to do.

All OSes expose it, type mount on Linux and it will list where each file system 
is mounted.
                
> 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
>              Labels: newbie
>         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

        

Reply via email to