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

Chanhae Oh updated FLINK-41509:
-------------------------------
    Component/s: Runtime / Coordination
                     (was: Runtime / Web Frontend)

> [historyserver] Web dashboard static assets are written flat into 
> historyserver.web.tmpdir instead of a dedicated subdirectory
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-41509
>                 URL: https://issues.apache.org/jira/browse/FLINK-41509
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Chanhae Oh
>            Priority: Minor
>             Fix For: 2.5.0
>
>         Attachments: image-2026-11-15-19-16-22-740.png
>
>
> !image-2026-11-15-19-16-22-740.png!
> While verifying FLIP-584 (FLINK-41285), I noticed the web dashboard's static 
> assets (JS/CSS, index.html, favicon, etc.) are written directly into the root 
> of historyserver.web.tmpdir, next to the archive data itself — see 
> AbstractHistoryServerHandler#respondToRequest / #tryLoadFromClassloader, 
> which resolves these files straight under rootPath on a cache miss.
> This is pre-existing behavior (since FLINK-1579), unrelated to 
> FLIP-584/ArchiveStorage, and not a correctness bug — the files are cleared on 
> every HistoryServer restart. It's just cosmetic clutter and muddies 
> file-count comparisons between storage backends.
> Suggested fix: serve/cache static assets under a dedicated subdirectory (e.g. 
> <tmpdir>/static/) by changing the rootPath passed to 
> AbstractHistoryServerHandler in HistoryServer#createFileHandlerFactory / 
> #createRocksDBHandlerFactory. Looks like a small, self-contained change — no 
> new config option needed.



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

Reply via email to