[
https://issues.apache.org/jira/browse/HDFS-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron T. Myers updated HDFS-6281:
---------------------------------
Attachment: HDFS-6281.patch
Attached patch implements this improvement basically by just emulating what the
DN does - optionally use jsvc to start the NFS Gateway as root, bind to a low
port for later use in portmap registration, drop privileges, then proceed to
start the NFS Gateway as normal but use the socket on the privileged port if it
exists.
No tests are included because to test this requires a system rpcbind to play
with, root access, etc. I tested this manually to ensure both that this patch
allows the NFS Gateway to register with an rpcbind version affected by the
relevant bug, and by ensuring that the NFS Gateway still works when used in
conjunction with the Hadoop-provided portmap daemon. It works as expected.
> Provide option to use the NFS Gateway without having to use the Hadoop
> portmapper
> ---------------------------------------------------------------------------------
>
> Key: HDFS-6281
> URL: https://issues.apache.org/jira/browse/HDFS-6281
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: nfs
> Affects Versions: 2.4.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: HDFS-6281.patch
>
>
> In order to use the NFS Gateway on operating systems with the rpcbind
> privileged registration bug, we currently require users to shut down and
> discontinue use of the system-provided portmap daemon, and instead use the
> portmap daemon provided by Hadoop. Alternately, we can work around this bug
> if we tweak the NFS Gateway to perform its port registration from a
> privileged port, and still let users use the system portmap daemon.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
