You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2014/12/07 02:23:12 UTC

[jira] [Created] (REEF-69) More fine-grained JVM options control

Markus Weimer created REEF-69:
---------------------------------

             Summary: More fine-grained JVM options control
                 Key: REEF-69
                 URL: https://issues.apache.org/jira/browse/REEF-69
             Project: REEF
          Issue Type: Improvement
            Reporter: Markus Weimer


REEF Evaluators and Drivers take over the whole memory of their host container as part of the JVM heap. This has bitten us in the past when Netty's buffers pushed us over the memory limit, which (on YARN) results in killed containers.

As a remedy, we added the JVM heap "slack" option, to leave some memory unallocated to the heap. This "solved" the issue at hand, but is hardly a principled solution.

Also, this is fundamentally an application concern, not one that REEF can generically solve. Consider {{Tasks}} that spawn processes as an example: In that case, the majority of the container memory should be used for that process, not the JVM hosting the {{Task}}.

Hence, we should add fine-grained control over the JVM startup options to the REEF API. 



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