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

Siddharth Seth updated TEZ-1941:
--------------------------------
    Attachment: TEZ-1941.1.txt

Simple patch which moves the memory specifications over to main methods - 
instead of accessing Runtime.maxmemory from within context instances. Also 
fixes some findbugs-warnings in runtime-internals introduced by moving TezChild 
from tez-dag.
Applies on top of TEZ-1879.

[~hitesh] - please review.

> Memory provided by *Context.getAvailableMemory needs to be setup explicitly
> ---------------------------------------------------------------------------
>
>                 Key: TEZ-1941
>                 URL: https://issues.apache.org/jira/browse/TEZ-1941
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: TEZ-1941.1.txt
>
>
> *Contexts.getAvailableMemory rely on Runtime..getMaxMemory(). This doesn't 
> work for memory scaling if multiple tasks are running within a JVM.
> Container sizes (sent over RPC) can be used for setting up this value.



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

Reply via email to