Idris,

You are right. Retry is not supported for subworkflow action.  JIRA OOZIE-797 
will track the bug in error codes picked up from oozie-site and 
oozie-default.xml.

Thanks for your inputs,

Mona


On 3/30/12 1:59 AM, "Idris Ali" <[email protected]> wrote:

No,

My requirement was to add retry to action of type subflow, I checked the
oozie code and it looks like Acton retries are supported for actions which
extend JavaActionExecutor and action of type subworkflowActionExecutor does
not support retries.

Thanks,
-Idris

On Fri, Mar 30, 2012 at 7:46 AM, Mona Chitnis <[email protected]> wrote:

>  Hi Idris,
>
> My teammate Michelle tested out the subworkflow retry. The parent workflow
> is not retried though the child workflow gets retried. Is that your case?
>
> This issue is being tracked in OOZIE-797 now.
>
> Thanks,
>
> Mona
>
>
>
> On 3/29/12 8:05 AM, "Idris Ali" <[email protected]> wrote:
>
> Hi Mona,
>
> Can you please let me know if action retries works in case of sub-flow
> action:
>
> My action in parent workflow looks like this:
>     <action name="user-workflow" retry-max="2" retry-interval="1">
>         <sub-workflow>
>             <app-path>${nameNode}/examples/apps/aggregator</app-path>
>             <propagate-configuration/>
>         </sub-workflow>
>         <ok to="ivory-succeeded-messaging"/>
>         <error to="ivory-failed-messaging"/>
>     </action>
>
> In this case, the workflow action was not retried.
>
> Thanks,
> -Idris
>
> On Thu, Mar 29, 2012 at 3:37 PM, Mona Chitnis <[email protected]>
> wrote:
>
> >  Hi Idris,
> >
> > I am still investigating if this is a configuration/packaging issue. If
> > not, I will go ahead and file a JIRA by tomorrow.
> >
> > Thanks for your feedback,
> >
> > Mona
> >
> >
> >
> > On 3/29/12 1:22 AM, "Idris Ali" <[email protected]> wrote:
> >
> > Thanks Mona,
> >
> > Do you want me to file a jira for this issue?
> >
> > -Idris
> >
> > On Thu, Mar 29, 2012 at 1:29 PM, Mona Chitnis <[email protected]>
> > wrote:
> >
> > > Yes Idris, properties in oozie-default work with lower precedence
> > compared
> > > to oozie-site. We are currently looking into this particular issue of
> > > certain error codes not getting picked up for action retry from
> > > oozie-default.
> > >
> > > --
> > > Mona
> > >
> > >
> > > On 3/29/12 12:31 AM, "Idris Ali" <[email protected]> wrote:
> > >
> > > Thanks, Michelle,
> > >
> > > Setting this property explicitly in oozie-site.xml seems to work. I was
> > in
> > > a impression that properties present in oozie-default.xml are always
> used
> > > as default. :-)
> > >
> > > -Idris
> > >
> > > On Thu, Mar 29, 2012 at 10:05 AM, Idris Ali <[email protected]>
> > wrote:
> > >
> > > > Thanks Michelle,
> > > >
> > > > I am gonna try this now, but I do not know why the same value present
> > in
> > > > oozie-default.xml is not working.
> > > >
> > > > -Idris
> > > >
> > > >
> > > > On Thu, Mar 29, 2012 at 12:29 AM, Michelle Chiang <
> > [email protected]
> > > >wrote:
> > > >
> > > >> Hi Idris,
> > > >>
> > > >> Could you please try this:
> > > >>
> > > >> Add the following property to oozie-site.xml, restart oozie, and run
> > > your
> > > >> test again and see if the action gets to "USER_RETRY" status.
> > > >>
> > > >>    <property>
> > > >>
> > > >>
> > >
> >
>  <name>oozie.service.LiteWorkflowStoreService.user.retry.error.code</name>
> > > >>        <value>JA008,JA009,JA017,JA018,JA019,FS009,FS008</value>
> > > >>    </property>
> > > >>
> > > >>
> > > >> Thanks
> > > >> michelle
> > > >>
> > > >> -----Original Message-----
> > > >> From: Idris Ali [mailto:[email protected] <[email protected]><
> [email protected]>]
> > > >> Sent: Wednesday, March 28, 2012 5:38 AM
> > > >> To: [email protected];
> [email protected]
> > > >> Subject: Retry of Action workflow doesn't work
> > > >>
> > > >> Hi,
> > > >>
> > > >> I am trying to test action retries based on this:
> > > >>
> > > >>
> > >
> >
> http://yahoo.github.com/oozie/releases/3.1.0/WorkflowFunctionalSpec.html#a18_User-Retry_for_Workflow_Actions_since_Oozie_3.1
> > > >>
> > > >> Environment:
> > > >> Oozie: apache oozie incubator 3.1.3 from
> > > >> http://incubator.apache.org/oozie/Downloads.html.
> > > >> Hadoop: cdh3u0
> > > >>
> > > >> Steps to reproduce:
> > > >> 1. Modified the pig-action's workflow.xml  available in oozie's
> > > examples:
> > > >> to change the namespace URI to <workflow-app
> > > >> xmlns="uri:oozie:workflow:0.3"
> > > >> name="pig-wf">
> > > >> 2. Added retry-max and retry-interval.
> > > >>    <action name="pig-node" retry-max="3" retry-interval="1"> 3.
> > > Commented
> > > >> prepare tag, to introduce error: JA018
> > > >>            <!--<prepare>
> > > >>                <delete
> > > >>
> path="${nameNode}/user/${wf:user()}/${examplesRoot}/output-data/pig"/>
> > > >>            </prepare>-->
> > > >> 4. oozie-default.xml remains as it is, but also tried by changing
> the
> > > >> value  of property
> > > oozie.service.LiteWorkflowStoreService.user.retry.max in
> > > >> oozie-default.xml
> > > >>
> > > >> However, when I run this, as expected we get Error JA018 in pig
> > action.
> > > >> But I do not see oozie retrying the failed action again, neither in
> > > oozie
> > > >> nor in hadoop.
> > > >>
> > > >> What additional settings are required to test retry actions? my
> > > >> requirement is to retry subflow for 10 times and then proceed to
> next
> > > >> action.
> > > >>
> > > >> Thanks,
> > > >> -Idris
> > > >>
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > *mona
> > **chitnis
> > *software developer
>
> >
> > [email protected]
> > direct 408-336-7908    mobile 864-650-0100
> >
> > 701 first avenue, sunnyvale, ca, 94089-0703, us
> > phone (408) 349 3300    fax (408) 349 3301
> >
> >
> >
>
>
> --
> *mona
> **chitnis
> *software developer
>
> [email protected]
> direct 408-336-7908    mobile 864-650-0100
>
> 701 first avenue, sunnyvale, ca, 94089-0703, us
> phone (408) 349 3300    fax (408) 349 3301
>
>
>

--
mona
chitnis
software developer

[email protected]
direct 408-336-7908    mobile 864-650-0100

701 first avenue, sunnyvale, ca, 94089-0703, us
phone (408) 349 3300    fax (408) 349 3301

[cid:3415965234_76404591]

Reply via email to