Configure and Start Apache Oozie
Upgrading Apache Oozie is a complex process. Although the instructions are straightforward, set aside a dedicated block of time to upgrade oozie clients and servers.
Perform the following preparation steps on each oozie server host:
You must restore oozie-site.xml from your backup to the conf directory on each oozie server and client.
Copy the JDBC jar to libext-customer.
Create the /usr/hdp/current/oozie/libext-customer directory.
cd /usr/hdp/current/oozie mkdir libext-customer
Grant read/write/execute access to all users for the libext-customer directory.
chmod -R 777 /usr/hdp/current/oozie/libext-customer
Copy these files to the libext-customer directory:
cp /usr/hdp/current/hadoop/lib/hadooplzo*.jar /usr/hdp/current/oozie/libext-customer
cp /usr/share/HDP-oozie/ext-2.2.zip /usr/hdp/current/oozie/libext-customer/
Extract share-lib.
cd /usr/hdp/current/oozie
tar xzvf /usr/hdp/current/oozie/oozie-sharelib.tar.gz
su -l hdfs -c "hdfs dfs -mkdir -p /user/oozie"su -l hdfs -c "hdfs dfs -copyFromLocal
/usr/hdp/current/oozie/share /user/oozie/."
You can expect to see messages stating that some files already exist. Delete any existing /oozie/share and replace it with the newly-extracted files.
su -l hdfs -c "hdfs dfs -chown oozie:hadoop /user/oozie"
su -l hdfs -c "hdfs dfs -chmod -R 755 /user/oozie"
if a previous version of Oozie was created using auto schema creation, run the following SQL query:
insert into oozie_sys (name, data) values ('db.version', '2.5');
As the Oozie user (not root), run the upgrade.
su $OOZIE_USER
/usr/hdp/current/oozie-server/bin/ooziedb.sh upgrade -run
As root, prepare the Oozie WAR file.
sudo su -l oozie -c "/usr/hdp/current/oozie/bin/oozie-setup.sh prepare-war -d /usr/hdp/current/oozie/libext-customer"
Look for console output to indicate success. For example, if you are using MySQL you should see something similar to:
INFO: Adding extension: libext-customer/mysql-connector-java.jar New Oozie WAR file with added 'JARs' at /var/lib/oozie/oozie-server/webapps/oozie.war
Add the following property to oozie-log4j.properties:
log4j.appender.oozie.layout.ConversionPattern=%d{ISO8601} %5p %c{1}:%L - SERVER[${oozie.instance.id}] %m%n
where ${oozie.instance.id} is determined by oozie, automatically.
As the oozie user, start Oozie:
sudo su -l <OOZIE_User> -c "cd /grid/0/var/log/oozie; /usr/hdp/current/oozie/oozie-server/bin/catalina.sh /usr/hdp/current/oozie/oozie-server/bin/setclasspath.sh /usr/hdp/current/oozie-server/bin/oozied.sh start"
Check processes.
ps -ef | grep -i oozie