[OOZIE-3153] Bundle example going to SUSPENDED instead of a terminal state

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

Environment

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

• Assignee: Unassigned
• Reporter: Andras Piros
• Created: 04/Jan/18 11:13
• Updated: 04/Jan/18 13:06
• Resolved: 04/Jan/18 13:06

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.