:
container_1469709900068_0002_01_01
2016-07-28 17:08:50,674 INFO
org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor: Exit code: 2
2016-07-28 17:08:50,674 INFO
org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor: Stack trace:
ExitCodeException exitCode=2:
Thanks,
Rahul Chhiber
ill occurs intermittently. Containers getting killed due to excess memory
consumption is understandable but if Node manager crashes in this manner it
would be a serious scalability problem.
Thanks,
Rahul Chhiber
Hi Xuan,
I applied the patch for YARN-3103 and the issue hasn't occurred since. Thanks
for your help! :)
Regards,
Rahul Chhiber
From: Xuan Gong [mailto:xg...@hortonworks.com]
Sent: Friday, February 06, 2015 5:53 AM
To: user@hadoop.apache.org
Subject: Re: Application Master fails due to Invalid
client from cache:
org.apache.hadoop.ipc.Client@552d7308
2015-02-04 12:56:03,544
[org.eclipse.jetty.server.session.HashSessionManager@425af55fTimer]
org.eclipse.jetty.server.session-DEBUG-Scavenging sessions at 1423054563544
Any help is greatly appreciated.
Thanks,
Rahul Chhiber
/hadoop/yarn/applications/distributedshell
Regards,
Rahul Chhiber
From: Sajid Syed [mailto:sajid...@gmail.com]
Sent: Thursday, December 18, 2014 9:44 AM
To: user@hadoop.apache.org
Subject: How to handle Container crash in YARN
Hello,
Can any please explain me how to handle/Resolve the Container
