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

chenzihao commented on FLINK-41286:
-----------------------------------

Hi, [~sumin] . Thanks a lot for the detailed testing and analysis — your 
diagnosis is correct. I'll create a JIRA and fix it by sharing the lazy-fetch 
task registry and executors between the two fetchers.

> Release Testing: Verify FLIP-585: Introduce Lazy Loading for HistoryServer
> --------------------------------------------------------------------------
>
>                 Key: FLINK-41286
>                 URL: https://issues.apache.org/jira/browse/FLINK-41286
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: chenzihao
>            Assignee: Sumin Joo
>            Priority: Blocker
>              Labels: release-testing
>             Fix For: 2.4.0
>
>
> Options:
> - \{{historyserver.archive.load.mode}} = EAGER (default) | LAZY
> Steps:
> 1. Prepare a large number of archives (e.g a complex topology or multiple 
> failovers).
> 2. Start with LAZY; verify the job list appears quickly, before all downloads 
> finish.
> 3. Open a not-yet-downloaded job; verify it is fetched on demand and renders 
> correctly.
> 4. Test LAZY with both FILE and ROCKSDB storage types.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to