[
https://issues.apache.org/jira/browse/SAMZA-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747123#comment-14747123
]
Navina Ramesh commented on SAMZA-368:
-------------------------------------
Yeah. [~closeuris] is right. SAMZA-619 refactors a lot of the AppMaster code.
Hopefully, this patch can wait until SAMZA-619 goes in.
> AM UI should show failed container information
> ----------------------------------------------
>
> Key: SAMZA-368
> URL: https://issues.apache.org/jira/browse/SAMZA-368
> Project: Samza
> Issue Type: Bug
> Components: yarn
> Reporter: Chris Riccomini
> Assignee: Aleksandar Bircakovic
> Attachments: SAMZA-368.0.patch, screenshot-samza-368.png
>
>
> All of the most important pieces of information are buried in the AM logs,
> and not displayed in the UI.
> The AM UI should display all failed containers, along with their exit codes,
> stack traces, etc. For example:
> {noformat}
> Dump of the process-tree for container_1407358862713_0021_01_000002 :
> |- PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS)
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE
> |- 21565 593 21565 21565 (java) 48828 1620 11089313792 2120985
> /export/apps/jdk/JDK-1_8_0_5/bin/java...
> Container killed on request. Exit code is 143
> Container exited with a non-zero exit code 143
> {noformat}
> This stuff will help people debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
