[
https://issues.apache.org/jira/browse/HDFS-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645322#comment-13645322
]
Brandon Li commented on HDFS-4750:
----------------------------------
@Han{quote}..not having understood the description in the pdf that "Hadoop+FUSE
could be used to provide an NFS interface for HDFS. However it has many known
problems and limitations."{quote}
For example, FUSE is not inode based like NFS. FUSE usually uses path to
generate the NFS file handle. Its path-handle mapping can make the host run out
of memory. Even it can work around the memory problem, it could have
correctness issue. FUSE may not be aware that a file's path has been changed by
other means(e.g., hadoop CLI). If FUSE is used on the client side, each NFS
client has to install a client component which runs only on Linux so far. ...
> Support NFSv3 interface to HDFS
> -------------------------------
>
> Key: HDFS-4750
> URL: https://issues.apache.org/jira/browse/HDFS-4750
> Project: Hadoop HDFS
> Issue Type: New Feature
> Affects Versions: 3.0.0
> Reporter: Brandon Li
> Assignee: Brandon Li
> Attachments: HADOOP-NFS-Proposal.pdf, nfs-trunk.patch
>
>
> Access HDFS is usually done through HDFS Client or webHDFS. Lack of seamless
> integration with client’s file system makes it difficult for users and
> impossible for some applications to access HDFS. NFS interface support is one
> way for HDFS to have such easy integration.
> This JIRA is to track the NFS protocol support for accessing HDFS. With HDFS
> client, webHDFS and the NFS interface, HDFS will be easier to access and be
> able support more applications and use cases.
> We will upload the design document and the initial implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
