[SAMZA-368] AM UI should show failed container information

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: yarn
• Assignee: Aleksandar Bircakovic
• Reporter: Chris Riccomini
• Created: 07/Aug/14 23:09
• Updated: 19/Oct/15 21:29
• Resolved: 19/Oct/15 21:29

Description

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:

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

This stuff will help people debug.

Issue Links

• depends upon: SAMZA-619 Modify Samza AppMaster to enable host-affinity