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

Todd Lipcon commented on HDFS-4750:
-----------------------------------

bq. For the second question, as long as the second user uses NFS gateway to 
read the closed file, the second user should be able to get the data buffered 
in NFS gateway

This precludes having multiple NFS gateways in operation simultaneously for 
increased throughput, right? I'd imagine the typical deployment scenario would 
be to run an NFS gateway on every machine and then have them mount localhost in 
order to avoid a bottleneck scenario. Even in a data loading situation, I'd 
expect a set of several "gateway nodes" to be used in round-robin in order to 
increase ingest throughput beyond what a single host can handle.
                
> 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
>
>
> 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

Reply via email to