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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/01/02 19:39:00 UTC
[jira] [Commented] (YARN-9148) AggregatedLogDeletion doesnt work
with S3
[ https://issues.apache.org/jira/browse/YARN-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732362#comment-16732362 ]
Steve Loughran commented on YARN-9148:
--------------------------------------
that's because directories don't actually exist: something just gets made up I'm afraid
> AggregatedLogDeletion doesnt work with S3
> -----------------------------------------
>
> Key: YARN-9148
> URL: https://issues.apache.org/jira/browse/YARN-9148
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bibin A Chundatt
> Priority: Critical
>
> Aggregated Log deletion works based on modification time of application directory
> S3AFileStatus give current time in case of directory.
> {code}
> if (appDir.isDirectory() &&
> appDir.getModificationTime() < cutoffMillis) {
> ApplicationId appId = ApplicationId.fromString(
> {code}
> S3AFileStatus#getModificationTime
> {code}
> @Override
> public long getModificationTime(){
> if(isDirectory()){
> return System.currentTimeMillis();
> } else {
> return super.getModificationTime();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org