AnsweredAssumed Answered

using hdfs-nfs-proxy on M3

Question asked by scratch28 on May 15, 2014
Latest reply on May 15, 2014 by Ted Dunning
I have an M3 installation and like the NFS mount.   I have no opportunity to upgrade to M5 or M7 but would like to have NFS mount on every node.
So I thought of using either fuse
or https://github.com/cloudera/hdfs-nfs-proxy

Fuse requires a NameNode - can the CLDB server act in this capacity ?

With hdfs-nfs-proxy
I get the following (after installing and following the instructions)

mount.nfs4: trying text-based options 'intr,timeo=600,port=2051,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx'
mount.nfs4: mount(2): Connection refused

/etc/fstab

xx.xx.xx.xx:/    /mnt/hdfs   nfs4       rw,intr,timeo=600,port=2051

output of error log

Exception: Required argument not found hdfs.nfs.security.allowed.hosts
        at com.cloudera.hadoop.hdfs.nfs.security.SecurityHandlerFactory.<init>(SecurityHandlerFactory.java:63)
        at com.cloudera.hadoop.hdfs.nfs.nfs4.NFS4Server.start(NFS4Server.java:91)
        at com.cloudera.hadoop.hdfs.nfs.nfs4.NFS4Server.run(NFS4Server.java:79)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
        at com.cloudera.hadoop.hdfs.nfs.nfs4.NFS4Server.main(NFS4Server.java:58)

Outcomes