Re: YARN on non-hdfs Error

2018-06-29 Thread Jeff Hubbs
I'm not sure what you're going for here, but the impression I get of what this parameter does tells me that if multiple machines write to it, things will explode. That would not be the case, however, if the developers coded mapreduce to make each machine name directories or files according to

Re: YARN on non-hdfs Error

2018-06-28 Thread Ascot Moss
Hi, Can "yarn.app.mapreduce.am.staging-dir" be set to use Linux shared mount point? if yes, is the following correct? mapred-site.xml yarn.app.mapreduce.am.staging-dir file:/share_mnt/tmp where "share_mnt" is the shared folder that can be accessed by all nodes. Please help!

Re: YARN on non-hdfs Error

2018-06-28 Thread Ascot Moss
* FYI, localFS here is shared disk mounted in CentOS.* I have also tired to use another mount point which is of ext4 format, I get similar error as */tmp/hadoop-yarn/staging/user_a/.staging/ is changed to 700 which is owned by user_a thus yarn cannot read it.* Any idea? On Thu, Jun 28, 2018 at

YARN on non-hdfs Error

2018-06-28 Thread Ascot Moss
Hi, I found that yarn can be used on non-hdfs file system. like AWS s3: or gfs I am trying yarn on localFS, *I use "yarn" user to start yarn on localFS (which is non-HDFS), and have other users to submit their own jobs, I got error* on *yarn.app.mapreduce.am.staging-dir permission:*