[
https://issues.apache.org/jira/browse/HDFS-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725945#comment-13725945
]
Colin Patrick McCabe commented on HDFS-4947:
--------------------------------------------
I think the most common case where you would run into multiple hostnames
mapping to a single IP is if you had an entry in {{/etc/hosts}}, and then also
a DNS server that had some entry. I think it would be easier to simply handle
this in this JIRA-- Brandon's suggestion of using the minimum access permission
seems fine to me. If you want to kick it down the road, I guess open another
JIRA.
> Add NFS server export table to control export by hostname or IP range
> ---------------------------------------------------------------------
>
> Key: HDFS-4947
> URL: https://issues.apache.org/jira/browse/HDFS-4947
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: nfs
> Affects Versions: 3.0.0
> Reporter: Brandon Li
> Assignee: Jing Zhao
> Attachments: HDFS-4947.000.patch, HDFS-4947.001.patch,
> HDFS-4947.002.patch, HDFS-4947.003.patch
>
>
> This jira adds NFS server export table (hostname or IP range) to control
> export. Specifically, it
> 1. adds two new classes AccessPrivilege and ClientHostsMatcher for loading
> and checking the mapping between client hosts and their access privileges.
> These two classes are directly copied from Brock Noland's NFS4 implementation.
> 2. adds the access check (based on the export) to NFS3 procedures.
--
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
