Hi Zihao, [1] Have you read through https://cwiki.apache.org/confluence/display/FLINK/FLIP+505%3A+Flink+History+Server+Scability+Improvements%2C+Remote+Data+Store+Fetch+and+Per+Job+Fetch? How does it relate to this work?
[2] There are some PRs for the FLIP-505 work which have been open for awhile here: https://github.com/apache/flink/pulls?q=is%3Apr+is%3Aopen+flip-505+37155 [3] Shouldn't the `get` method return a `String`? [4] I'm surprised by the high default thread counts for the lazy loader. I suppose you have some experience tuning that number? The rest of it looks reasonable. Cheers, Jim On Mon, Mar 23, 2026 at 8:02 AM zihao chen <[email protected]> wrote: > Hi all, > > I’d like to start a discussion on *FLIP-XXX: Enhancing HistoryServer with > Lazy Loading and Pluggable Storage*. > > This FLIP proposes improving the HistoryServer to address *slow > startup*, *delayed > job visibility*, and *excessive small files* when handling large numbers of > archived jobs. > > The proposal introduces: > > - *Lazy loading mode* for on-demand job archive fetching > - Optional *RocksDB-based storage* to reduce small files > > Compatibility: Full backward compatibility (EAGER + FILE as default) > > The detailed designs are described in the FLIP document: > > > https://docs.google.com/document/d/1FQn-HQSIdhio3ImeOrbS9VfB6JqRTrRV4ZEZDTf3K2o/edit?usp=sharing > > Looking forward to your feedback. > > > Best regards, > > Zihao Chen >
