hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "genericqa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13138) webhdfs of federated namenode does not work properly
Date Wed, 14 Feb 2018 05:06:00 GMT

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

genericqa commented on HDFS-13138:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red}  7m  6s{color} | {color:red}
Docker failed to build yetus/hadoop:ea57d10. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-13138 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12910504/HDFS-13138.002.branch-2.7.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/23058/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> webhdfs of federated namenode does not  work properly
> -----------------------------------------------------
>
>                 Key: HDFS-13138
>                 URL: https://issues.apache.org/jira/browse/HDFS-13138
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 2.7.1, 3.0.0
>            Reporter: KWON BYUNGCHANG
>            Priority: Major
>         Attachments: HDFS-13138.001.branch-2.7.patch, HDFS-13138.001.patch, HDFS-13138.002.branch-2.7.patch,
HDFS-13138.002.patch
>
>
> my cluster has multiple namenodes using HDFS Federation.
> webhdfs that is not defaultFS does not work properly.
> when I uploaded to non defaultFS namenode  using webhdfs.
> uploaded file was founded at defaultFS namenode.
>  
> I think root cause is that
>   clientNamenodeAddress of non defaultFS namenode is always fs.defaultFS.
>  [https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java#L462]
>  
> {code:java}
> /**
>    * Set the namenode address that will be used by clients to access this
>    * namenode or name service. This needs to be called before the config
>    * is overriden.
>    */
>   public void setClientNamenodeAddress(Configuration conf) {
>     String nnAddr = conf.get(FS_DEFAULT_NAME_KEY);
>     if (nnAddr == null) {
>       // default fs is not set.
>       clientNamenodeAddress = null;
>       return;
>     }
>     LOG.info("{} is {}", FS_DEFAULT_NAME_KEY, nnAddr);
>     URI nnUri = URI.create(nnAddr);
>     String nnHost = nnUri.getHost();
>     if (nnHost == null) {
>       clientNamenodeAddress = null;
>       return;
>     }
>     if (DFSUtilClient.getNameServiceIds(conf).contains(nnHost)) {
>       // host name is logical
>       clientNamenodeAddress = nnHost;
>     } else if (nnUri.getPort() > 0) {
>       // physical address with a valid port
>       clientNamenodeAddress = nnUri.getAuthority();
>     } else {
>       // the port is missing or 0. Figure out real bind address later.
>       clientNamenodeAddress = null;
>       return;
>     }
>     LOG.info("Clients are to use {} to access"
>         + " this namenode/service.", clientNamenodeAddress );
>   }
> {code}
>  
> so webhdfs is redirected to datanode having wrong namenoderpcaddress parameter
> finally file was located namenode of fs,defaultFS
>  
> workaround is
>   configure fs.defaultFS of each namenode to its own nameservice.  
> e.g.
>   hdfs://ns1  has fs.defaultFS=hdfs://ns1
>   hdfs://ns2  has fs.defaultFS=hdfs://ns2
>   ....
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message