You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/11/27 05:55:58 UTC

[jira] [Commented] (OOZIE-1089) DistributedCache workaround for Hadoop 2.0.2-alpha

    [ https://issues.apache.org/jira/browse/OOZIE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504374#comment-13504374 ] 

Alejandro Abdelnur commented on OOZIE-1089:
-------------------------------------------

Riding on the fact that all JARs in the current directory of the launcher job will be implicitly part of the distributed cache of the action job, we can create a workaround until MAPREDUCE-4820 is fixed. The workaround would remove the distributed cache settings from the action configuration.

This workaround behavior would only be activated if a flag is set in oozie-site.xml.

                
> DistributedCache workaround for Hadoop 2.0.2-alpha
> --------------------------------------------------
>
>                 Key: OOZIE-1089
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1089
>             Project: Oozie
>          Issue Type: Bug
>          Components: workflow
>    Affects Versions: 3.3.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 3.3.0
>
>
> As explained in MAPREDUCE-4820, Hadoop 2.0.2-alpha introduced a duplicate check that exposes an change of behavior in how the distributed-cache works in Hadoop 2 (as opposed to Hadoop-1).

--
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