[
https://issues.apache.org/jira/browse/HDFS-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053087#comment-14053087
]
Abhiraj Butala commented on HDFS-6456:
--------------------------------------
I am not sure if this is a valid issue. 'host1-rw' itself is treated as the
hostname. Since the hostname and the permissions are not separated by white
spaces, it is treated as if permissions are not provided for this hostname. By
default, read-only permission is assumed in this case.
Following are relevant comments from NfsExports.java:
{code}
/**
* Loading a matcher from a string. The default access privilege is read-only.
* The string contains 1 or 2 parts, separated by whitespace characters, where
* the first part specifies the client hosts, and the second part (if
* existent) specifies the access privilege of the client hosts. I.e.,
*
* "client-hosts [access-privilege]"
*/
{code}
The fix for HDFS-6455 shall log an error for invalid exports, like invalid
separators.
> NFS: NFS server should throw error for invalid entry in
> dfs.nfs.exports.allowed.hosts
> -------------------------------------------------------------------------------------
>
> Key: HDFS-6456
> URL: https://issues.apache.org/jira/browse/HDFS-6456
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: nfs
> Affects Versions: 2.2.0
> Reporter: Yesha Vora
>
> Pass invalid entry in dfs.nfs.exports.allowed.hosts. Use - as separator
> between hostname and access permission
> {noformat}
> <property><name>dfs.nfs.exports.allowed.hosts</name><value>host1-rw</value></property>
> {noformat}
> This misconfiguration is not detected by NFS server. It does not print any
> error message. The host passed in this configuration is also not able to
> mount nfs. In conclusion, no node can mount the nfs with this value. A format
> check is required for this property. If the value of this property does not
> follow the format, an error should be thrown.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
