Pleas don't cross post.
Common is BCCed. Each container has a vmem limit that is enforced, but not in
local mode. If this is for the app master then you can increase this amount so
that when you launch your AM you can set this amount through
SubmitApplicationRequest req; ...
req.getApplicationSubmissionContext().getAMContainerSpec().getResource().setMemory(memory_in_mb)
--Bobby Evans
On 1/5/12 12:44 AM, "raghavendhra rahul" <raghavendhrara...@gmail.com> wrote:
Hi,
I am trying to start an server within the application master's
container alone.But when i tried using Runtime.getRuntime.exec("command").But
it throws the following execption.
Application application_1325738010393_0003 failed 1 times due to AM Container
for appattempt_1325738010393_0003_000001 exited with exitCode: 143 due to:
Container [pid=7212,containerID=container_1325738010393_0003_01_000001] is
running beyond virtual memory limits. Current usage: 118.4mb of 1.0gb physical
memory used; 2.7gb of 2.1gb virtual memory used. Killing container. Dump of the
process-tree for container_1325738010393_0003_01_00000
When i tried using single node yarn cluster everything works fine.But in multi
node it throws this exception.Should i increase the size of /tmp in linux.......
Any ideas????
