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

Flink Jira Bot updated FLINK-28643:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> 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
>              Labels: pull-request-available, stale-assigned
>         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)

Reply via email to