Re: yarn kill container due to running beyond physical memory limits [ How can i debug memory issue ]

Posted by Alexis Gendronneau on
URL: http://deprecated-apache-flink-user-mailing-list-archive.369.s1.nabble.com/yarn-kill-container-due-to-running-beyond-physical-memory-limits-How-can-i-debug-memory-issue-tp7296p7326.html

thats kinda strange. Have you tried setting minimum allocations for containers to a bigger size too ?

2016-06-02 0:04 GMT+02:00 prateekarora <[hidden email]>:

Hi

I have not changed any configuration "yarn.heap-cutoff-ratio" or
"yarn.heap-cutoff-ratio.min" .

As per log  flink assign 4608 M out of 6 GB .  i thought  configuration
working fine .
/usr/lib/jvm/java-7-oracle-cloudera/bin/java -Xms4608m -Xmx4608m
-XX:MaxDirectMemorySize=4608m


Regards
Prateek
-



--
View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/yarn-kill-container-due-to-running-beyond-physical-memory-limits-How-can-i-debug-memory-issue-tp7296p7325.html

Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.

--