[FALCON-350] Not possible to "re-schedule" a process which failed

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5
• Component/s: process
• Assignee: Unassigned
• Reporter: Jean-Baptiste Onofré
• Created: 12/Mar/14 12:09
• Updated: 14/Jul/14 10:26
• Resolved: 14/Jul/14 10:26

Description

When scheduling a process (with bin/falcon entity -schedule -type process -name my-process), and the bundle job fails in Oozie (for any reason), the process entity is in submitted status:

bin/falcon entity -status -type process -name my-process
default/SUBMITTED

If we try to schedule it again:

bin/falcon entity -schedule -type process -name my-process
default/my-process(process) scheduled successfully

we have "successfully", but the process is still in submitted status and nothing happens on Oozie (no new bundle job created):

bin/falcon entity -status -type process -name my-process
default/SUBMITTED

The only way is to delete the process, submit it, and finally schedule it again.

It would be great to add a "-force" option or try to force re-schedule when status is submitted.

Thoughts ?

Issue Links

• is part of: FALCON-353 enable dry run feature of oozie for schedule and update