[ https://issues.apache.org/jira/browse/TEZ-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386316#comment-15386316 ]
Kuhu Shukla commented on TEZ-3345: ---------------------------------- [~Sreenath] Thanks a lot. bq. - Wouldn't the diagnostic message from RM fits better in app details? If I understand the question correctly, showing the diagnostics on {{tez-app/application_123_456}} details page would also work, although I am not sure if we have a diagnostics section in the Application Details section. > Diagnostics for a failed AM may not show up on the DAG UI page. > --------------------------------------------------------------- > > Key: TEZ-3345 > URL: https://issues.apache.org/jira/browse/TEZ-3345 > Project: Apache Tez > Issue Type: Improvement > Components: UI > Reporter: Kuhu Shukla > Attachments: DagPage_AMDiagnostics.png > > > In a scenario where AM fails on all its attempts, the DAG page does not show > the Diagnostics message on the Tez UI "Diagnostics" section. The messageis > available on the AHS and could be pulled into the DAG page just like we do > for failed vertices. > I ran a simple Tez example job that was given way too less memory causing the > AM to fail: > {code} > hadoop jar /home/gs/tez/current/tez-examples-0.7.1.x.x.jar orderedwordcount > -Dtez.am.resource.memory.mb=16 -Dtez.am.launch.cmd-opts="-Xmx13m > -Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails > -XX:+PrintGCDateStamps -Xloggc:<LOG_DIR>/gc.log"/books /output > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)