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

Xintong Song commented on FLINK-28307:
--------------------------------------

I've drafted a release note for this feature.

{code}
We have enhanced the experiences of viewing completed jobs’ information in this 
release.
- JobManager / HistoryServer WebUI now provides detailed execution time 
metrics, including durations tasks spend in each execution state and the 
accumulated busy / idle / back-pressured time during running.
- JobManager / HistoryServer WebUI now provides aggregation of major SubTask 
metrics, grouped by Task or TaskManager.
- JobManager / HistoryServer WebUI now provides more environmental information, 
including environment variables, JVM options and classpath.
- HistoryServer now supports browsing logs from external log archiving 
services. For more details: 
https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/deployment/advanced/historyserver#log-integration
{code}



> FLIP-241: Completed Jobs Information Enhancement
> ------------------------------------------------
>
>                 Key: FLINK-28307
>                 URL: https://issues.apache.org/jira/browse/FLINK-28307
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / REST, Runtime / Web Frontend
>            Reporter: Yangze Guo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> Streaming and Batch users have different interests in probing a job. While 
> streaming users mainly care about the instant status of a running job (tps, 
> delay, backpressure, etc.), batch users care more about the overall job 
> status during the entire execution (queueing / execution time, total data 
> amount, etc.).
> As Flink grows into a unified streaming & batch processor and is adopted by 
> more and more batch users, the experiences in inspecting completed jobs has 
> become more important than ever.
> We compared Flink with other popular batch processors, and spotted several 
> potential improvements. Most of these changes involves WebUI & REST API 
> changes, which should be discussed and voted on as FLIPs. However, creating 
> separated FLIPs for each of the improvement might be overkill, because 
> changes needed by each improvement are quite small. Thus, we include all 
> these potential improvements in this one FLIP.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to