[
https://issues.apache.org/jira/browse/TEZ-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279419#comment-14279419
]
Hitesh Shah commented on TEZ-1941:
----------------------------------
Any reason why the memory getter was not added to the execution context object
itself?
> 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)
