[jira] [Updated] (YARN-4309) Add debug information to application logs when a container fails

["Varun Vasudev (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Varun Vasudev updated YARN-4309:
--------------------------------
    Attachment: YARN-4309.003.patch

Uploaded a new patch that adds a section on broken symlinks to the directory info.

> Add debug information to application 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
>         Attachments: YARN-4309.001.patch, YARN-4309.002.patch, YARN-4309.003.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)