MapR 5.0 Documentation : Manage Oozie Services and Interface

This topic contains the following sections:

Starting and Stopping Oozie Services

The Warden daemon starts the Oozie server automatically at installation time. You can start and stop Oozie in the following ways:

  • Using the maprcli node services command, you can start Oozie on multiple nodes at one time.
  • Using the MapR Control System

Whenever you change the cluster MapReduce mode (from Yarn to Classic, or from Classic to Yarn), you must restart the Oozie server.

To start Oozie using the maprcli:

  1. Make a list of nodes on which Oozie is configured.
  2. Issue the maprcli node services command, specifying the nodes on which Oozie is configured, separated by spaces. Example:

    maprcli node services -name oozie -action start -nodes node001 node002 node003

To stop Oozie using the maprcli:

  1. Make a list of nodes on which Oozie is configured.
  2. Issue the maprcli node services command, specifying the nodes on which Oozie is configured, separated by spaces. Example:

    maprcli node services -name oozie -action stop -nodes node001 node002 node003

To start Oozie using the MapR Control System:

  1. In the Navigation pane, expand the Cluster Views pane and click Dashboard.
  2. In the Services pane, click Oozie to open the Nodes screen displaying all the nodes on which Oozie is configured.
  3. On the Nodes screen, click the hostname of each node to display its Node Properties screen.
  4. On each Node Properties screen, use the Stop/Start button in the Oozie row under Manage Services to start Oozie.

Enabling the Oozie Web UI

The Oozie Web UI can display your job status, logs, and other related information. You must enable the Oozie Web UI after you install Oozie. However, depending on how you enable the Web UI, you may also need to perform manual steps to start the Web UI after you run configure.sh on the cluster.

Perform the following steps to enable the Oozie Web UI:

  1. Download the Ext JS 2.2 library as a zip archive (ext-2.2.zip) from this location.

    The Ext JS 2.2 library is required only for the Oozie Web UI. Note that a rewrite of the Oozie web UI has been proposed in the Oozie user community.

  2. Copy the Ext JS 2.2 library into the libext directory: 

    cp ext-2.2.zip /opt/mapr/oozie/oozie-<version>/libext
  3. Perform one of the following options based on your preference:

    1. If you want the Oozie Web UI to start whenever Oozie starts or restarts, perform the following steps:
      1. If Oozie is running, shut it down:

        maprcli node services -name oozie -action stop -nodes <space delimited list of nodes>
      2. Run the oozie-setup.sh script, and specify the hadoop version.

        /opt/mapr/oozie/oozie-<version>/bin/oozie-setup.sh -hadoop <version> /opt/mapr/hadoop/hadoop-<version>
    2. If you want to manually start the Web UI when Oozie starts or restarts, perform the following steps:

      1. If Oozie is running, shut it down:

        maprcli node services -name oozie -action stop -nodes <space delimited list of nodes>
      2. Run the oozie-setup.sh script and specify the path to the extjs file.

        cd /opt/mapr/oozie/oozie-<version>
        bin/oozie-setup.sh prepare-war -extjs <path to file>/ext-2.2.zip
  4. Start Oozie.

    maprcli node services -name oozie -action start -nodes <space delimited list of nodes>

Checking the Status of Oozie

Once Oozie is installed, you can check the status using the command line or the Oozie web console.

To check the status of Oozie using the command line:

  • Use the oozie admin command:

    /opt/mapr/oozie/oozie-<version>/bin/oozie admin -oozie http://<oozie_node>:11000/oozie -status

    The following output indicates normal operation:

    System mode: NORMAL

To check the status of Oozie using the web console:

  • Point your browser to http://<oozie_node>:11000/oozie

Attachments:

ManageOozie.png (image/png)