[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056515#comment-15056515 ]
Wangda Tan edited comment on YARN-4309 at 12/14/15 7:19 PM: ------------------------------------------------------------ Committed to trunk/branch-2. Thanks [~vvasudev] and review from [~ste...@apache.org]/[~sidharta-s]/[~aw]/[~jlowe]/[~kasha]! was (Author: leftnoteasy): Committed to trunk/branch-2. Thanks [~vvasudev] and review from [~ste...@apache.org]/[~sidharta-s]/[~aw]! > Add container launch related debug information to container logs when a > container fails > --------------------------------------------------------------------------------------- > > Key: YARN-4309 > URL: https://issues.apache.org/jira/browse/YARN-4309 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager > Reporter: Varun Vasudev > Assignee: Varun Vasudev > Fix For: 2.8.0 > > Attachments: YARN-4309.001.patch, YARN-4309.002.patch, > YARN-4309.003.patch, YARN-4309.004.patch, YARN-4309.005.patch, > YARN-4309.006.patch, YARN-4309.007.patch, YARN-4309.008.patch, > YARN-4309.009.patch, YARN-4309.010.patch > > > Sometimes when a container fails, it can be pretty hard to figure out why it > failed. > My proposal is that if a container fails, we collect information about the > container local dir and dump it into the container log dir. Ideally, I'd like > to tar up the directory entirely, but I'm not sure of the security and space > implications of such a approach. At the very least, we can list all the files > in the container local dir, and dump the contents of launch_container.sh(into > the container log dir). > When log aggregation occurs, all this information will automatically get > collected and make debugging such failures much easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)