[
https://issues.apache.org/jira/browse/HDFS-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726099#comment-13726099
]
Jing Zhao commented on HDFS-4947:
---------------------------------
Actually here my original question is how to identify the multiple hostnames
mapped to the given ip address. Looks like we need to get all the available
nameservice providers and use them to identify all the possible hostnames. In
java's InetAddress, before JDK 7 only the first successfully-loaded nameservice
will be used. In JDK 7, a list of providers are loaded and sorted according to
the system property "sun.net.spi.nameservice.provider.n", but
InetAddress#getCanonicalHostName will still only return one hostname. So I
guess here we can reuse the nameservice loading code from JDK 7, and use
all/part of the nameservices to get those possible hostnames for a given IP.
What do you guys think?
> 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
