Created a JIRA here.
https://issues.apache.org/jira/browse/YARN-76
On Thu, Aug 30, 2012 at 1:43 PM, Bo Wang wrote:
> The calling graph is very useful. Thanks, Vinod.
>
> I traced the code and enabled debugging log. I found one thing interesting
> here.
>
> While running the AM, I "ps aux | grep
The calling graph is very useful. Thanks, Vinod.
I traced the code and enabled debugging log. I found one thing interesting
here.
While running the AM, I "ps aux | grep SampleAM". I found two running
processes.
34990
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
Samp
Please attach your jstack dump, may be I can spot something.
Pointer for what you asked: ContainerManagerImpl.stopContainer() ->
ContainerImpl.KillTransition -> ContainersLauncher ->
ContainerLaunch.cleanupContainer(). Follow the events carefully.
HTH,
+Vinod
On Aug 29, 2012, at 3:28 PM, Bo W
Hi Vinod,
Thanks for the suggestion. I was involved with some other issues before
getting back to this one. Sorry for replying late.
I tried to kill the process with "kill -3" but it was not interrupted. Then
I used "kill -9" which sent a SIGKILL and the process was killed. I checked
the stderr a
> I am not sure when to grab the stack trace of the AM. In the stdout/stderr
> of AM, no stack trace (or exception) is emitted.
You can login to the node and if the process is still alive, you can do a "kill
-3" which will dump the threads' status to stderr.
> Btw, I am curious how NM kills a
Thanks for looking into this, Arun.
I am not sure when to grab the stack trace of the AM. In the stdout/stderr
of AM, no stack trace (or exception) is emitted.
Btw, I am curious how NM kills a container. Does it directly kill the JVM
process?
Thanks,
Bo
On Wed, Aug 22, 2012 at 4:22 PM, Arun C M
Did you grab a stack trace of the AM?
On Aug 22, 2012, at 4:01 PM, Bo Wang wrote:
> Hello,
>
> I have an AM listening to a port. I kill the application by sending a
> request via ClientRMProtocol # killApplication. In the NM log, the
> corresponding container of AM transitions from RUNNING to KI
