Skip to main content

Oozie says jar does not exist

After submitting an oozie shell action job, oozie logs say shell-launcher.jar does not exist.

JA008: File /var/tmp/oozie/oozie-oozi450698329702305.dir/shell-launcher.jar does not exist.

On the oozie server shell-luncher.jar exists in the local folder.

# locate shell-launcher.jar
/usr/local/oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/oozie-server/temp/oozie-root3458733450304809568234.dir/shell-launcher.jar

In order to resolve this error, just crate hdfs folders and give appropriate permissions to them.

# su -l hdfs -c "hadoop fs -mkdir /var"
# su -l hdfs -c "hadoop fs -mkdir /var/tmp"
# su -l hdfs -c "hadoop fs -mkdir /var/tmp/oozie"
# su -l hdfs -c "hadoop fs -chmod -R 755 /var"
# su -l hdfs -c "hadoop fs -chown oozie:hdfs /var/tmp/oozie"

Comments

  1. In case of me, /var/tmp/oozie should exist on local file system, not on HDFS.
    After creating the directory, restart the Oozie server. Then there comes a lot of files under /var/tmp/oozie including *-launcher.jar files.

    '/var/tmp/oozie' is the value of -Djava.io.tmpdir variable of Oozie server start-up command line. You can check the value using 'ps -ef | grep oozie' where the Oozie server is running.

    ReplyDelete

Post a Comment

Popular posts from this blog