hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13469) RBF: Support InodeID in the Router
Date Thu, 19 Apr 2018 03:09:00 GMT

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

Xiao Chen commented on HDFS-13469:

Thanks folks for bringing up this issue.

Is it even possible to solve this in a compatible way?

Suppose I'm the client and I previously read from {{/.reserved/inode/123}}, from the only
nameservice I had. Now the cluster is federated and another nameservice is added. Router based
or not, if that other nameservice also has inode 123, there is no way that my input {{/.reserved/inode/123}}
can map to the 2 inodes in the 2 nameservices, both ID'ed 123...

It seems to me we'd require the client to explicitly read from {{hdfs://nameserviceX/.reserved/inode/123}}
to have this working, and call out this in documentation.

I'm not very familiar with NFS, does HDFS-11575 address this?

> RBF: Support InodeID in the Router
> ----------------------------------
>                 Key: HDFS-13469
>                 URL: https://issues.apache.org/jira/browse/HDFS-13469
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Íñigo Goiri
>            Priority: Major
> The Namenode supports identifying files through inode identifiers.
> Currently the Router does not handle this properly, we need to add this functionality.

This message was sent by Atlassian JIRA

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

View raw message