Yuliya Feldman created TWILL-252:
------------------------------------
Summary: Not providing any feedback when size of the container
requested can't be allocated
Key: TWILL-252
URL: https://issues.apache.org/jira/browse/TWILL-252
Project: Apache Twill
Issue Type: Bug
Reporter: Yuliya Feldman
Looks like when YARN is configured with max memory per container
(yarn.scheduler.maximum-allocation-mb) less then amount of memory end user
allocates for their application and container is allocated with just
yarn.scheduler.maximum-allocation-mb value there is no way to know about it
until container is allocated.
We try to divide memory into heap and off-heap and end up with setting up off
heap to the value higher then allocated for the container, as application
assumes it gets what it asked for or container is not allocated at all.
Need either ability to fail application in this case or not allocate container
with memory less then asked.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
