You can use any directory you like beside permissions are right.
*Warm Regards_**∞_* * Shashwat Shriparv* [image: http://www.linkedin.com/pub/shashwat-shriparv/19/214/2a9]<http://www.linkedin.com/pub/shashwat-shriparv/19/214/2a9>[image: https://twitter.com/shriparv] <https://twitter.com/shriparv>[image: https://www.facebook.com/shriparv] <https://www.facebook.com/shriparv>[image: http://google.com/+ShashwatShriparv] <http://google.com/+ShashwatShriparv>[image: http://www.youtube.com/user/sShriparv/videos]<http://www.youtube.com/user/sShriparv/videos>[image: http://profile.yahoo.com/SWXSTW3DVSDTF2HHSRM47AV6DI/] <shrip...@yahoo.com> On Mon, Mar 3, 2014 at 11:07 AM, Chengwei Yang <chengwei.yang...@gmail.com>wrote: > Hi List, > > I'm confusing by hadoop.tmp.dir currently because its default value > "/tmp/hadoop-${user.name}" always means a directory in tmpfs in Linux. > So after the name node machine reboot, it gone away and then name node > fail to start. > > I found this was reported here. > > http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-user/201205.mbox/%3cbay148-w22bf95c5fbe2c40bf7cd9f86...@phx.gbl%3E > > As I found from http://hadoop.apache.org/docs/r2.3.0/, there are a lot > properties are based on hadoop.tmp.dir, like > dfs.namenode.name.dir file://${hadoop.tmp.dir}/dfs/name > > I'm wondering, if we can set the default value of hadoop.tmp.dir to > a non-tmpfs direcotry if it doesn't work at all by using a real tmpfs > directory? > > -- > Thanks, > Chengwei >
