You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/07/08 19:12:00 UTC

[jira] [Comment Edited] (FLINK-18097) History server doesn't clean all job json files

    [ https://issues.apache.org/jira/browse/FLINK-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153865#comment-17153865 ] 

Chesnay Schepler edited comment on FLINK-18097 at 7/8/20, 7:11 PM:
-------------------------------------------------------------------

master: 78d6ee1cef6d9c0d5d28e4e228f7050de1c6c7a2
1.11: d64a5a0c2566416158c67719dc08d7623e14fad8
1.10: 0e7278929bcf08e4e51f791a34c0220709c5e6ad 


was (Author: zentol):
master: 78d6ee1cef6d9c0d5d28e4e228f7050de1c6c7a2
 1.11: d64a5a0c2566416158c67719dc08d7623e14fad8

1.10: 0e7278929bcf08e4e51f791a34c0220709c5e6ad 

> History server doesn't clean all job json files
> -----------------------------------------------
>
>                 Key: FLINK-18097
>                 URL: https://issues.apache.org/jira/browse/FLINK-18097
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / REST
>    Affects Versions: 1.10.1
>            Reporter: Milan Nikl
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.10.2, 1.12.0, 1.11.1
>
>
> Improvement introduced in https://issues.apache.org/jira/browse/FLINK-14169 does not delete all files in the history server folders completely.
> There is a [json file created for each job|https://github.com/apache/flink/blob/master/flink-runtime-web/src/main/java/org/apache/flink/runtime/webmonitor/history/HistoryServerArchiveFetcher.java#L237-L238] in history server's {{webDir/jobs/}} directory. Such file is not deleted by {{cleanupExpiredJobs}}.
> And while the cleaned up job is no longer visible in History server's {{Completed Jobs List}} in web UI, it can be still accessed on {{<HistoryServerURL>/#/job/<jobId>/overview}}.
> While this bug probably won't lead to any serious issues, files in history server's folders should be cleaned up thoroughly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)