[jira] [Issue Comment Deleted] (FALCON-350) Not possible to "re-schedule" a process which failed

["Shwetha G S (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FALCON-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shwetha G S updated FALCON-350:
-------------------------------

    Comment: was deleted

(was: I will handle this as part of FALCON-345)

> Not possible to "re-schedule" a process which failed
> ----------------------------------------------------
>
>                 Key: FALCON-350
>                 URL: https://issues.apache.org/jira/browse/FALCON-350
>             Project: Falcon
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 0.5
>            Reporter: Jean-Baptiste Onofré
>
> 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:
> {code}
> bin/falcon entity -status -type process -name my-process
> default/SUBMITTED
> {code}
> If we try to schedule it again:
> {code}
> bin/falcon entity -schedule -type process -name my-process
> default/my-process(process) scheduled successfully
> {code}
> we have "successfully", but the process is still in submitted status and nothing happens on Oozie (no new bundle job created):
> {code}
> bin/falcon entity -status -type process -name my-process
> default/SUBMITTED
> {code}
> 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 ?



--
This message was sent by Atlassian JIRA
(v6.2#6252)