[
https://issues.apache.org/jira/browse/OOZIE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463342#comment-13463342
]
Robert Kanter commented on OOZIE-994:
-------------------------------------
The test failure is caused by:
{code}
Caused by: java.lang.IllegalArgumentException: Pathname
/user/test/oozie-jenk/0000000-120925224647405-oozie-jenk-W/:start:--:START:
from
hdfs://localhost:44005/user/test/oozie-jenk/0000000-120925224647405-oozie-jenk-W/:start:--:START:
is not a valid DFS filename.
at
org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:132)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:513)
at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:768)
at
org.apache.oozie.command.wf.ResumeXCommand.execute(ResumeXCommand.java:89)
....
{code}
Line 89 in ResumeXCommand.java is:
{code}
ActionExecutorContext context = new
ActionXCommand.ActionExecutorContext(workflow, action, false,false); // line 88
if (context.getAppFileSystem().exists(context.getActionDir())) { // line 89
context.getAppFileSystem().delete(context.getActionDir(), true); // line 90
}
{code}
I'm not sure why this didn't happen locally. It looks like the problem is that
this was called on a start action, which is {{:start:}} and I imagine that the
colon is not allowed in a filename; I'll have to make it check for these types
of actions (e.g. start, end, etc).
> 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,
> 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
