[
https://issues.apache.org/jira/browse/YARN-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254905#comment-16254905
]
Prabhu Joseph commented on YARN-7500:
-------------------------------------
[~jlowe] Oh yes, missed it.
The issue is our customer has a long running custom Yarn Application which has
started before yarn.log-aggregation.retain-seconds and was running yesterday as
per the RM UI, and today we din see any logs under app-logs. Logs where there
for running job. Looks only possibility is the custom app has not updated the
logs for many days.
Will check RM logs and hdfs-audit logs to validate and give more information.
> LogAggregation DeletionService should consider completedTime for long running
> jobs
> ----------------------------------------------------------------------------------
>
> Key: YARN-7500
> URL: https://issues.apache.org/jira/browse/YARN-7500
> Project: Hadoop YARN
> Issue Type: Bug
> Components: log-aggregation
> Affects Versions: 2.7.3
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
>
> Currently LogAggregation deletes the application logs based on start time of
> the job. For long running jobs (started before
> yarn.log-aggregation.retain-seconds), say it is failed yesterday for some
> reason and we won't have the job logs today for debugging.
> Better to consider the completedTime of the job as part of the deletion
> condition.
--
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
