Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.incubator.apache.org
Date: Wed, 12 Mar 2014 12:10:42 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12700937.1394626169702.50815.1394626242512@arcas>
In-Reply-To: <JIRA.12700937.1394626169702@arcas>
References: <JIRA.12700937.1394626169702@arcas>
Subject: [jira] [Created] (FALCON-350) Not possible to "re-schedule" a
 process which failed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Jean-Baptiste Onofr=C3=A9 created FALCON-350:
-------------------------------------------

             Summary: 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=C3=A9


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 p=
rocess 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 no=
thing 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 a=
gain.

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)