[
https://issues.apache.org/jira/browse/OOZIE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460192#comment-13460192
]
Virag Kothari commented on OOZIE-994:
-------------------------------------
Had a discussion with Mohammad. Will summarize it
When the retry is being done, the status can be kept RUNNING (The good thing is
ActionCheckerService will re-queue RUNNING actions if something bad happens)
Once its suspended and retry is done, the status can be set to 'START_MANUAL'
(As the action has to be started through ActionStartX in ResumeX)
Basically, referring to the following code change.
{code}
if (!handleTransient(context, executor, wfAction.getStatus)) //
wfAction.getStatus() should be always RUNNING I believe?{
handleNonTransient(context, executor, START_MANUAL); // Having START_MANUAL
will make the user know he has to resume the action manually
{code}
> ActionCheckXCommand does not handle failures properly
> -----------------------------------------------------
>
> Key: OOZIE-994
> URL: https://issues.apache.org/jira/browse/OOZIE-994
> Project: Oozie
> Issue Type: Bug
> Components: workflow
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Assignee: Robert Kanter
> Priority: Critical
> Fix For: trunk
>
> Attachments: OOZIE-994.patch
>
>
> If the JT restarts or dies and running jobs are lost or the JT is not
> reachable, Oozie ActionCheckXCommand will never fail the workflow job.
> There seem to be 2 issues here:
> * convertException is not receiving the root cause exception anytmore, but
> alway HadoopAccessorException wrapping the root cause exception. We should
> modify the convertException to inspect the cause exception as well.
> * ActionCheckXCommand does not do the handle retry logic of
> ActionStartXCommand.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
