hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2219) Fsck should work with fully qualified file paths.
Date Fri, 05 Aug 2011 06:25:27 GMT

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

Uma Maheswara Rao G commented on HDFS-2219:

Hi Jitendra,

 Currently fsck implementation will not depend on path URIs to communicate with NN.

Below is the snippet where it is getting the current namenode address to communicate.

 String namenodeAddress = getCurrentNamenodeAddress();
    if (namenodeAddress == null) {
      //Error message already output in {@link #getCurrentNamenodeAddress()}
      System.err.println("DFSck exiting.");
      return 0;


To handle the Federation support , there is one issue HDFS-1700.
But i did not see the complete code merged in trunk from HDFS-1700 subversion commits.

You mean, we can get the NN address from URI if available?
Correct me if i understud wrongly :-)


> Fsck should work with fully qualified file paths.
> -------------------------------------------------
>                 Key: HDFS-2219
>                 URL: https://issues.apache.org/jira/browse/HDFS-2219
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 0.23.0
>            Reporter: Jitendra Nath Pandey
>            Priority: Minor
> Fsck takes absolute paths, but doesn't work with fully qualified file path URIs. In a
federated cluster with multiple namenodes, it will be useful to be able to specify a file
path for any namenode using its fully qualified path. Currently, a non-default file system
can be specified using -fs option.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message