xintongsong commented on PR #19712: URL: https://github.com/apache/flink/pull/19712#issuecomment-1138239988
Hi @Airblader, I'm not an expert in frontend techniques, thus have not reviewed this PR. But I can share some background on this. @yangjunhan and I are working together preparing a serial of Flink History Server improvements. History server was not very crucial when Flink mainly focused on streaming workloads, but is becoming a weakness with more and more batch workloads supported. And one of the major aspects that the history server needs to improve is the UI and interactions. Currently, Flink history server simply reuses the runtime WebUI. This leads to poor experiences. - Not all information / functions are available after the job finishes. E.g., memory footprints, busy/idle/back-pressure status, flame-graph, etc. Leaving these unavailable information / functions on the WebUI confuses users. - With the unavailable things taking the page spaces, those users truly care after the job finishes are separated into different pages, requires more clicks or page switchings to access. On the other hand, history server and runtime WebUIs do share many things in common, which makes re-creating a new WebUI from scratch for history server makes less sense. I believe this is where the idea making WebUI components configurable and customizable comes from. FYI, the history server improvements are still in preparation and we don't have a FLIP to present at the moment. But I did put it into the [1.16 feature plan](https://cwiki.apache.org/confluence/display/FLINK/1.16+Release). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
