question Re: Mapreduce job failure due to hadoop-unjarxxxxxx directory under /tmp in Support Questions

Mapreduce job failure due to hadoop-unjarxxxxxx directory under /tmp

banshidhar_saho — Tue, 30 Apr 2019 12:02:42 GMT

Hi Team,

We are facing an issue where mapreduce jobs are failing with below error.

Distribution: Cloudera (CDH 5.14.4)

====

Exception in thread "main" java.io.FileNotFoundException: /tmp/hadoop-unjar5272208588996002870/org/apache/hadoop/hive/metastore/api/ThriftHiveMetastore$AsyncClient$revoke_privileges_call.class (No space left on device)

at java.io.FileOutputStream.open0(Native Method)

at java.io.FileOutputStream.open(FileOutputStream.java:270)

at java.io.FileOutputStream.<init>(FileOutputStream.java:213)

at java.io.FileOutputStream.<init>(FileOutputStream.java:162)

at org.apache.hadoop.util.RunJar.unJar(RunJar.java:110)

at org.apache.hadoop.util.RunJar.unJar(RunJar.java:81)

at org.apache.hadoop.util.RunJar.run(RunJar.java:214)

at org.apache.hadoop.util.RunJar.main(RunJar.java:141)

====

We figured out that MR framework tries to keep temporary class files under /tmp dir with a folder named hadoop-unjarxxxxxx.

As there is not enough space in /tmp to hold the class files, it fails with above error.

We want to change the default location for hadoop-unjarxxxxxx directory.

We changed the default value of hadoop.tmp.dir in core-site.xml (safety valve) to /ngs/app/${user.name}/hadoop/tmp , but it’s of no help.

Any suggestion on how to change the default hadoop-unjar location from /tmp to something else.

Regards,

Banshi.

Re: Mapreduce job failure due to hadoop-unjarxxxxxx directory under /tmp

bgooley — Tue, 30 Apr 2019 17:18:51 GMT

Hi @banshidhar_saho ,

Since the stack trace shows RunJar.java being used, that indicates the Java option you need is:

java.io.tmpdir

If you can se that in your "Java Configuration" safety valves for Yarn that should help.

Since we don't see the whole stack trace in your post, we can't tell which safety valve would apply to that situation exactly.

Re: Mapreduce job failure due to hadoop-unjarxxxxxx directory under /tmp

banshidhar_saho — Thu, 02 May 2019 12:18:02 GMT

Hi @bgooley ,

Thank you for your suggestion.

We set the same property and it fixed the issue.

Cloudera Manager --> YARN --> searched for: Gateway Client Environment Advanced Configuration Snippet (Safety Valve) for hadoop-env.sh and added this:

HADOOP_CLIENT_OPTS="-Djava.io.tmpdir=/ngs/app/$(whoami)/hadoop/tmp"

Regards,

Banshi.

Re: Mapreduce job failure due to hadoop-unjarxxxxxx directory under /tmp

Abhilash — Wed, 31 Jul 2019 04:21:55 GMT

Hello ,

We are facing the same issue in our production environment. Is this creation of temp files is default behaviour and we can't change it ?. As we are running multiple concurrent sessions at same point of time we are facing multiple job failures with with this inodes issue . Is there any other solution we have instead of changing the path.

I just want to know in what cases the folder will be created . We are using hive cli, beeline , hadoop shell commands and sqoop process in our project.

We have observed that the default behaviour will delete the folders automatically as soon as the activity complete.but some times some folders are not getting deleted and occupying more inodes (12k) for folder structure.

Please help to make us understand .

Thanks in advance.

Re: Mapreduce job failure due to hadoop-unjarxxxxxx directory under /tmp

sow — Tue, 05 Nov 2019 06:42:11 GMT

hi Abhilash,

I am facing same issue while running concurrent sessions at the same point.
Did u find a solution to change the temp directory ?