Installing Oozie

This topic includes instructions for using package managers to download and install Oozie from the MEP repository.

For instructions on setting up the MEP repository, see Step 10: Install Ecosystem Components Manually.

Oozie's client/server architecture requires you to install two packages, mapr-oozie and mapr-oozie-internal, on the client node and the server node. mapr-oozie is dependent on

mapr-oozie-internal.
        mapr-oozie-internal

is automatically installed by the package manager when you install mapr-oozie.

Execute the following commands as root or using sudo on a HPE Ezmeral Data Fabric cluster:

Install mapr-oozie and mapr-oozie-internal:

RedHat/CentOS

yum install mapr-oozie mapr-oozie-internal

SUSE

zypper install mapr-oozie mapr-oozie-internal

Ubuntu

apt-get install mapr-oozie mapr-oozie-internal

For non-secure clusters, add the following two properties to core-site.xml located in /opt/mapr/hadoop/hadoop-2.x.x/etc/hadoop/core-site.xml:

<property>
  <name>hadoop.proxyuser.mapr.hosts</name>
  <value>*</value>
</property>
<property>
  <name>hadoop.proxyuser.mapr.groups</name>
  <value>*</value>
</property>

Restart the YARN services. For YARN mode, restart NodeManager and ResourceManager:

maprcli node services -name nodemanager -action restart -nodes <space delimited list of nodes>
maprcli node services -name resourcemanager -action restart -nodes <space delimited list of nodes>

Run configure.sh -R:
```
/opt/mapr/server/configure.sh -R
```
On client or edge nodes installed with MEP 6.3.1 or MEP 7.0.0 or later, run the following configure.sh command:
For secure clusters, use:
```
/opt/mapr/oozie/oozie-5.1.0/bin/configure.sh -R -c --secure
```
For non-secure clusters, use:
```
/opt/mapr/oozie/oozie-5.1.0/bin/configure.sh -R -c --unsecure
```

Export the Oozie URL to your environment:

For secure clusters, use:

export OOZIE_URL='<https://<Oozie_node>:<oozie_port_number>/oozie'>
where <oozie_port_number>=11443

For non-secure clusters, use:

export OOZIE_URL='<http://<Oozie_node>:<oozie_port_number>/oozie'>
where <oozie_port_number>=11000

Check Oozie’s status with the following command:

/opt/mapr/oozie/oozie-<version>/bin/oozie admin -status

If high availability for the Resource Manager is configured, edit the job.properties file for each workflow and insert the following statement
```
JobTracker=maprfs:///
```
If high availability for the Resource Manager is not configured, provide the address of the node running the active ResourceManager and the port used for ResourceManager client RPCs (port 8032). For each workflow, edit the job.properties file and insert the following statement:
```
JobTracker=<ResourceManager_address>:8032
```
Restart Oozie:
```
maprcli node services -name oozie -action restart -nodes <space delimited list of nodes>
```
Note: If high availability for the Resource Manager is not configured and the ResourceManager fails, you must update the job.properties with the active ResourceManager.