[
https://issues.apache.org/jira/browse/HDFS-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500430#comment-16500430
]
Daryn Sharp commented on HDFS-13469:
------------------------------------
{quote}opaque handles to files/directories and use those for directory
enumeration/traversal, fetching block locations, etc.
{quote}
Please elaborate on how this might work? Ie. What is and how does the opaque
thing map to the underlying namesystem? How will a compatible and simple
traversal work?
{quote}Option two, we hack it into inodeid and continue using the magic path.
If there are other options then let's explore them
{quote}
The only compatible approach is conceptually partitioning the inode id ranges
to disambiguate the location of the inode id. Simplest implementation is
namesystems use distinct non-overlapping ranges but that only works for new
namespaces.
Auto-magically re-writing inode ids is probably a necessary evil. Router can
enumerate namespaces using the upper bits of the inode ids. Proxied rpc
responses mask on the namespace id bits, proxied rpc requests must strip off
the bits. (Exception is router has to own the root inode id)
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
