You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 07:19:08 UTC

[jira] [Created] (OOZIE-336) GH-535: RFE: API for Detecting Failed Action in Workflow

GH-535: RFE: API for Detecting Failed Action in Workflow
--------------------------------------------------------

                 Key: OOZIE-336
                 URL: https://issues.apache.org/jira/browse/OOZIE-336
             Project: Oozie
          Issue Type: Bug
            Reporter: Hadoop QA


When a work-flow fails, the user has to manually scan the logs to determine the failing action and (after having taken appropriate measures) re-submit the work-flow starting at the failed action.

Provide an automated mechanism for detecting the failed action in an instance. This could be used by wrapper scripts or Jobs to, for example, work around transient failures without involving manual intervention.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Reopened] (OOZIE-336) GH-535: RFE: API for Detecting Failed Action in Workflow

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik reopened OOZIE-336:
------------------------------------


> GH-535: RFE: API for Detecting Failed Action in Workflow
> --------------------------------------------------------
>
>                 Key: OOZIE-336
>                 URL: https://issues.apache.org/jira/browse/OOZIE-336
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> When a work-flow fails, the user has to manually scan the logs to determine the failing action and (after having taken appropriate measures) re-submit the work-flow starting at the failed action.
> Provide an automated mechanism for detecting the failed action in an instance. This could be used by wrapper scripts or Jobs to, for example, work around transient failures without involving manual intervention.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-336) GH-535: RFE: API for Detecting Failed Action in Workflow

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101759#comment-13101759 ] 

Hadoop QA commented on OOZIE-336:
---------------------------------

rmathew remarked:
Yes, it does look like what I'm asking for here. From what I can make out, I'd be able to submit a work-flow instance via the Java API and then re-submit it upon failure using the API and setting an additional configuration property.

> GH-535: RFE: API for Detecting Failed Action in Workflow
> --------------------------------------------------------
>
>                 Key: OOZIE-336
>                 URL: https://issues.apache.org/jira/browse/OOZIE-336
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> When a work-flow fails, the user has to manually scan the logs to determine the failing action and (after having taken appropriate measures) re-submit the work-flow starting at the failed action.
> Provide an automated mechanism for detecting the failed action in an instance. This could be used by wrapper scripts or Jobs to, for example, work around transient failures without involving manual intervention.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-336) GH-535: RFE: API for Detecting Failed Action in Workflow

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100006#comment-13100006 ] 

Hadoop QA commented on OOZIE-336:
---------------------------------

anew remarked:
Issue 78 (https://github.com/yahoo/oozie/issues/78) added the ability to rerun a workflow from the failed node (without having to specify which nodes to skip). Does that address your need? If so, I would like to close this as a dup.

> GH-535: RFE: API for Detecting Failed Action in Workflow
> --------------------------------------------------------
>
>                 Key: OOZIE-336
>                 URL: https://issues.apache.org/jira/browse/OOZIE-336
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> When a work-flow fails, the user has to manually scan the logs to determine the failing action and (after having taken appropriate measures) re-submit the work-flow starting at the failed action.
> Provide an automated mechanism for detecting the failed action in an instance. This could be used by wrapper scripts or Jobs to, for example, work around transient failures without involving manual intervention.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (OOZIE-336) GH-535: RFE: API for Detecting Failed Action in Workflow

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadoop QA resolved OOZIE-336.
-----------------------------

    Resolution: Fixed

> GH-535: RFE: API for Detecting Failed Action in Workflow
> --------------------------------------------------------
>
>                 Key: OOZIE-336
>                 URL: https://issues.apache.org/jira/browse/OOZIE-336
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> When a work-flow fails, the user has to manually scan the logs to determine the failing action and (after having taken appropriate measures) re-submit the work-flow starting at the failed action.
> Provide an automated mechanism for detecting the failed action in an instance. This could be used by wrapper scripts or Jobs to, for example, work around transient failures without involving manual intervention.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira