Andras Piros commented on OOZIE-3298:

Changes in patch 004:
* removed new test inside {{TestJavaActionExecutor}}
* {{JavaActionExecutor#findEffectiveYarnApplicationId()}} now falls back to 
looking for an available YARN child application that isn't the launcher via 
{{YarnClient#getApplications()}} in case there is still no {{action-data.seq}} 
written by {{LauncherMain}} at the end of the MapReduce action
* {{TestMapReduceActionExecutor#startWorkflowAndFailChildMRJob()}} now waits 
until a real YARN child that isn't the Oozie Launcher appears

The test 
 fails locally. [~pbacsko] can you please look at the code and advise what do I 
have to change?

> OYA: external ID is not filled properly and failing MR job is treated as 
> ----------------------------------------------------------------------------------
>                 Key: OOZIE-3298
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3298
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 5.0.0
>            Reporter: Peter Bacsko
>            Assignee: Andras Piros
>            Priority: Blocker
>             Fix For: 5.1.0
>         Attachments: OOZIE-3298.001.patch, OOZIE-3298.002.patch, 
> OOZIE-3298.003.patch, OOZIE-3298.004.patch
> When a MapReduce action is launched from Oozie (OYA), we don't properly fill 
> the external ID field. It gets populated with the YARN id of the LauncherAM, 
> not with the id of the actual MR job. If the MR job is succesfully submitted 
> then fails, it will be treated as a successfully executed action, which is 
> very misleading and can potentially confuse Oozie users.

This message was sent by Atlassian JIRA

Reply via email to