You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2022/10/25 09:37:00 UTC

[jira] [Assigned] (FLINK-28643) Job archive file contains too much Job json file on Flink HistoryServer

     [ https://issues.apache.org/jira/browse/FLINK-28643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xintong Song reassigned FLINK-28643:
------------------------------------

    Assignee: LI Mingkun

> Job archive file contains too much Job json file on Flink HistoryServer 
> ------------------------------------------------------------------------
>
>                 Key: FLINK-28643
>                 URL: https://issues.apache.org/jira/browse/FLINK-28643
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Web Frontend
>    Affects Versions: 1.15.1
>            Reporter: LI Mingkun
>            Assignee: LI Mingkun
>            Priority: Major
>         Attachments: image-2022-07-22-17-04-55-046.png, image-2022-09-30-14-45-10-846.png, image-2022-10-13-16-39-25-887.png, image-2022-10-13-16-39-46-486.png
>
>
> h1. Problem
> In History Server, 'HistoryServerArchiveFetcher' fetch job archived file,and pass it into a job dir.
> There are more than 1w json files for big parallism job which run out of inodes
> !image-2022-10-13-16-39-46-486.png!
> h1. Suggestion
>  # Generate a big json file for each job instead of a lot of small json file
>  # Support lazy fetcher/unzip of archivedJobFile 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)