Oozie Commands
Oozie Commands
==============
sudo -u hdfs hdfs dfs -mkdir /user/hdpuser
sudo -u hdfs hdfs dfs -mkdir /user/hdpuser/oozie
sudo -u hdfs hdfs dfs -chown -R hdpuser:hdfs /user/hdpuser
sudo -u hdfs hdfs dfs -chmod -R 770 /apps
If you enable NFS Gateway, use below commands. Otherwise ignore this section:
=============================================================================
sudo mkdir /hdfs
sudo umount -l /hdfs
sudo mount -t nfs -o
vers=3,proto=tcp,nolock,sync,rsize=1048576,wsize=1048576,noatime localhost:/ /hdfs
In Oozie Node:
==============
hdfs dfs -ls /user/oozie/share/lib/
sudo -u oozie hdfs dfs -put /usr/share/java/mysql-connector-java.jar
/user/oozie/share/lib/lib_20181226065713/sqoop/
sudo -u oozie oozie admin -oozie http://hn3.hadoop.com:11000/oozie/ -sharelibupdate
export OOZIE_URL="http://hn3.hadoop.com:11000/oozie/"
du -sch /data/mysqlbakups/
df -h | grep /data
Timeout: A coordinator job can specify the timeout for its coordinator actions,
this is, how long the coordinator action will be in WAITING or READY status before
giving up on its execution.
Concurrency: A coordinator job can specify the concurrency for its coordinator
actions, this is, how many coordinator actions are allowed to run concurrently
( RUNNING status) before the coordinator engine starts throttling them.
Execution strategy: A coordinator job can specify the execution strategy of its
coordinator actions when there is backlog of coordinator actions in the coordinator
engine. The different execution strategies are 'oldest first', 'newest first' and
'last one only'. A backlog normally happens because of delayed input data,
concurrency control or because manual re-runs of coordinator jobs.
Throttle: A coordinator job can specify the materialization or creation throttle
value for its coordinator actions, this is, how many maximum coordinator actions
are allowed to be in WAITING state concurrently.