You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2018/01/04 11:14:00 UTC

[jira] [Created] (OOZIE-3153) Bundle example going to SUSPENDED instead of a terminal state

Andras Piros created OOZIE-3153:
-----------------------------------

             Summary: Bundle example going to SUSPENDED instead of a terminal state
                 Key: OOZIE-3153
                 URL: https://issues.apache.org/jira/browse/OOZIE-3153
             Project: Oozie
          Issue Type: Bug
          Components: examples
    Affects Versions: 5.0.0b1
         Environment: Oozie running on a developer box using a pseudo-distributed Hadoop 2.6.5 running on the very same machine
            Reporter: Andras Piros
            Priority: Minor
         Attachments: Screen Shot 2018-01-04 at 12.11.48 PM.png, Screen Shot 2018-01-04 at 12.12.17 PM.png, Screen Shot 2018-01-04 at 12.12.37 PM.png

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

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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)