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

Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2013/12/06 02:03:35 UTC

[jira] [Updated] (OOZIE-1634) TestJavaActionExecutor#testUpdateConfForUberMode fails against Hadoop 2

     [ https://issues.apache.org/jira/browse/OOZIE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kanter updated OOZIE-1634:
---------------------------------

    Attachment: OOZIE-1634.patch

The patch makes the test check for the {{-Xmx1024m}} when using Yarn but now when using MR1.

> TestJavaActionExecutor#testUpdateConfForUberMode fails against Hadoop 2
> -----------------------------------------------------------------------
>
>                 Key: OOZIE-1634
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1634
>             Project: Oozie
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Minor
>         Attachments: OOZIE-1634.patch
>
>
> {{TestJavaActionExecutor#testUpdateConfForUberMode}} fails against Hadoop 2.  
> It looks like the problem is that {{yarn.app.mapreduce.am.command-opts}} has a default value of {{-Xmx1024m}} in Hadoop 2 but (obviously) not in Hadoop 1.  So, when the test is verifying the value of {{yarn.app.mapreduce.am.command-opts}} after some code appends values to it, it now includes {{-Xmx1024m}} when run against Hadoop 2 but not when run against Hadoop 1; and so the test fails.



--
This message was sent by Atlassian JIRA
(v6.1#6144)