[
https://issues.apache.org/jira/browse/YARN-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Payne updated YARN-4422:
-----------------------------
Attachment: YARN-4422.001.patch
Attaching {{YARN-4422-001.patch}}. [~jeagles] or [~jlowe], would you mind
taking a look?
The problem was that when the Applications page in the Generic AHS renders, it
depends on a MASTER_CONTAINER_EVENT_INFO being in the AppAttemptReport. If it's
not there, it will give up on trying to print start time, node, or log lings.
The reason that information then appears when you clidk on the app attempt link
is because when the Application Attempt page renders, it just gets the whole
list of containers for the app attempt and prints that information for each
one, including the AM container, but it still doesn't have an indication which
one is the AM container.
The reason the MASTER_CONTAINER_EVENT_INFO isn't in the AppAttemptReport is
because that is provided by the REGISTER event in the System Metrics Publisher,
and since this use case doesn't ever get to the point of AM registration, the
MASTER_CONTAINER_EVENT_INFO isn't there.
However, in all of these cases, the RM container does get a FINISHED event. I
fixed this by adding the MASTER_CONTAINER_EVENT_INFO to the FINISHED event.
> Generic AHS sometimes doesn't show started, node, or logs on App page
> ---------------------------------------------------------------------
>
> Key: YARN-4422
> URL: https://issues.apache.org/jira/browse/YARN-4422
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Eric Payne
> Assignee: Eric Payne
> Attachments: AppAttemptPage no container or node.jpg, AppPage no logs
> or node.jpg, YARN-4422.001.patch
>
>
> Sometimes the AM container for an app isn't able to start the JVM. This can
> happen if bogus JVM options are given to the AM container (
> {{-Dyarn.app.mapreduce.am.command-opts=-InvalidJvmOption}}) or when
> misconfiguring the AM container's environment variables
> ({{-Dyarn.app.mapreduce.am.env="JAVA_HOME=/foo/bar/baz}})
> When the AM container for an app isn't able to start the JVM, the Application
> page for that application shows {{N/A}} for the {{Started}}, {{Node}}, and
> {{Logs}} columns. It _does_ have links for each app attempt, and if you click
> on one of them, you go to the Application Attempt page, where you can see all
> containers with links to their logs and nodes, including the AM container.
> But none of that shows up for the app attempts on the Application page.
> Also, on the Application Attempt page, in the {{Application Attempt
> Overview}} section, the {{AM Container}} value is {{null}} and the {{Node}}
> value is {{N/A}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
