[
https://issues.apache.org/jira/browse/HDFS-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000314#comment-14000314
]
Aaron T. Myers commented on HDFS-6406:
--------------------------------------
bq. SLF4J doesn't let you at the log4j appender behind a log, so switching to
log4j would break your test. The workaround there is to use commons logging in
the test and request the same log -which is what most of today's tests do. If
you stick with commons logging, it's a non-issue.
Note that the test does not actually rely on the increased log level - that was
just for convenience so that I could look at the logs after running it.
bq. this would be good time to replace the inline "nfs3.mountd.port", with a
constant.
Agreed, but I've been deliberately avoiding messing with the NFS-related
configs because HDFS-6056 is doing a larger cleanup of that whole thing.
Sounds like there are no objections to this patch, despite the inherent limits
of the approach. I'm going to go ahead and commit this shortly based on
Andrew's +1.
> Add capability for NFS gateway to reject connections from unprivileged ports
> ----------------------------------------------------------------------------
>
> Key: HDFS-6406
> URL: https://issues.apache.org/jira/browse/HDFS-6406
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: nfs
> Affects Versions: 2.4.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: HDFS-6406.patch, HDFS-6406.patch
>
>
> Many NFS servers have the ability to only accept client connections
> originating from privileged ports. It would be nice if the HDFS NFS gateway
> had the same feature.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
