file locks.
--Konstantin
--
View this message in context:
http://www.nabble.com/Problems-with-NFS-share-in-dfs.name.dir-tp15647255p17564617.html
Sent from the Hadoop core-user mailing list archive at Nabble.com.
You should probably check what is you OS and FS on the NFS share.
I did not see problems with NFS per se, but some (local) file systems do not
support file locks.
--Konstantin
prasana.iyengar wrote:
Using hadoop-0.16.0 I am having a similar problem in bringup.
I added a gluster mount point to
it works fine.
> But, if one of the directories is NFS mounted, we're having these
> problems:
>
> 1) "hadoop dfs -ls" takes 1-2 minutes to finish, and returns error:
--
View this message in context:
http://www.nabble.com/Problems-with-NFS-share-in-dfs.name.dir-tp15
Check the namenode log. It is possible that your NFS mount has problems
NameNode might be stuck trying to write to it.
If log is not useful, you can attach jstack output for NameNode when it
seems to be stuck.
Raghu.
Nathan Wang wrote:
Hi,
We're having problems when trying to deal with t
Hi,
We're having problems when trying to deal with the namenode failover, by
following the wiki
http://wiki.apache.org/hadoop/NameNodeFailover
If we point dfs.name.dir to 2 local directories, it works fine.
But, if one of the directories is NFS mounted, we're having these problems:
1) "hadoo
