You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Adam Antal (JIRA)" <ji...@apache.org> on 2019/07/15 09:58:00 UTC
[jira] [Assigned] (YARN-9675) Expose log aggregation diagnostic
messages through RM API
[ https://issues.apache.org/jira/browse/YARN-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Antal reassigned YARN-9675:
--------------------------------
Assignee: Adam Antal
> Expose log aggregation diagnostic messages through RM API
> ---------------------------------------------------------
>
> Key: YARN-9675
> URL: https://issues.apache.org/jira/browse/YARN-9675
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: api, log-aggregation, resourcemanager
> Affects Versions: 3.2.0
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
>
> The ResourceManager collects the log aggregation status reports from the NodeManagers. Currently these reports are collected, but when app info API or similar high-level REST is called, only an overall status is displayed (RUNNING, RUNNING_WITH_FAILURES,FAILED etc.).
> The diagnostic messages are only available through the old RM web UI, so our internal tool currently crawls that page and extract the log aggregation diagnostic and error messages from the raw HTML. This is not a good practice, and more elegant API call may be preferable. It may be useful for others as well since log aggregation related failures are usually hard to debug since the lack of trace/debug messages.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org