[
https://issues.apache.org/jira/browse/YARN-7027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du updated YARN-7027:
-----------------------------
Target Version/s: 2.8.3 (was: 2.8.2)
> Log aggregation finish time should get logged for trouble shooting.
> -------------------------------------------------------------------
>
> Key: YARN-7027
> URL: https://issues.apache.org/jira/browse/YARN-7027
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: log-aggregation
> Reporter: Junping Du
> Assignee: Junping Du
>
> Now, RM track application log aggregation status in RMApp and the status
> change is triggered by NM heartbeat with log aggregation report. For each
> node's log aggregation status change from in-progress
> (NOT_START,RUNNING,RUNNING_WITH_FAILURE) to final status (SUCCEEDED,FAILED,
> TIMEOUT), it trigger an aggregation for log aggregation status:
> updateLogAggregationStatus(). The whole progress is log less and we cannot
> trace the log aggregation problem (delay of log aggregation, etc.) from RM
> (or NM) log. We should add more log here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
