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 2015/09/26 02:07:04 UTC

[jira] [Created] (OOZIE-2372) YARN_MEMORY_MB_MIN for uber mode should be configurable

Robert Kanter created OOZIE-2372:
------------------------------------

             Summary: YARN_MEMORY_MB_MIN for uber mode should be configurable
                 Key: OOZIE-2372
                 URL: https://issues.apache.org/jira/browse/OOZIE-2372
             Project: Oozie
          Issue Type: Bug
          Components: core
    Affects Versions: 4.1.0
            Reporter: Robert Kanter


{{YARN_MEMORY_MB_MIN}} in {{JavaActionExeuctor}} is hardcoded to 512 (MB).  This is used when using uber mode like this:
{code:java}
int memoryMB = Math.max(launcherMapMemoryMB, amMemoryMB) + YARN_MEMORY_MB_MIN;
{code}
And {{memoryMB}} is then set for {{yarn.app.mapreduce.am.resource.mb}} to set the amount of memory the MR AM needs.

Because this is hardcoded to 512, on a really small cluster with limited memory (e.g. a single-node cluster VM), you may get an {{InvalidResourceRequestException}} when trying to submit the job.

A hacky way around this is to set {{oozie.launcher.yarn.app.mapreduce.am.resource.mb}} to a negative number, because we don't check for {{> 0}} and this subtracts from the hardcoded 512.  It would be better if we made {{YARN_MEMORY_MB_MIN}} configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)