[
https://issues.apache.org/jira/browse/OOZIE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462069#comment-13462069
]
Robert Kanter commented on OOZIE-994:
-------------------------------------
It increments the retries count so that in ResumeXCommand, we have a way of
differentiating this case from resuming from other reasons. We then set it to
0 in there. In other words, I'm kinda using it like a flag; if there's a
better way to detect this case in ResumeXCommand I'd have no problem with
changing it.
The reason I used two for loops was because of the case where the outer and
wrapped exceptions are both registered. If we check both in one for loop, then
the order that we iterate through the registered exceptions would determine
which one we picked. For example, if type1 was caused by type2 and both were
registered, we want type2 to be chosen but it could choose type1 depending on
their ordering in {{ERROR_INFOS}}.
> 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, OOZIE-994.patch, 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
