Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3153

Bundle example going to SUSPENDED instead of a terminal state

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Not A Problem
    • Affects Version/s: 5.0.0b1
    • Fix Version/s: None
    • Component/s: examples
    • Labels:
      None
    • Environment:

      Oozie running on a developer box using a pseudo-distributed Hadoop 2.6.5 running on the very same machine

      Description

      Steps to reproduce:

      1. Build Oozie 5.0.0-beta1 and install w/ Hadoop 2.6.5 in a pseudo-distributed way
      2. Install examples to HDFS
      3. Run bundle example like this:
        oozie job -oozie http://localhost:11000/oozie -config /path/to/examples/apps/bundle/job.properties -run -DnameNode=hdfs://localhost:9000 -DjobTracker=loclahost:8032
        

      Expected result: Oozie bundle job is run till some terminal state like SUCCEEDED, KILLED, or FAILED.

      Actual result: Oozie bundle job is stucked at SUSPENDED state, along with coordinator and workflow jobs belonging to that one.

      Note that this doesn't happen on a real Oozie cluster, using real Hadoop installation - in that case, bundle / coordinator / workflow jobs go to SUCCEEDED.

        Attachments

        1. OOZIE-3153.log
          13 kB
          Andras Piros
        2. Screen Shot 2018-01-04 at 12.11.48 PM.png
          100 kB
          Andras Piros
        3. Screen Shot 2018-01-04 at 12.12.17 PM.png
          232 kB
          Andras Piros
        4. Screen Shot 2018-01-04 at 12.12.37 PM.png
          224 kB
          Andras Piros

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              andras.piros Andras Piros
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: