[
https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825369#comment-17825369
]
Zhanghao Chen edited comment on FLINK-25068 at 3/11/24 4:04 PM:
----------------------------------------------------------------
Hi [~zlzhang0122][~lincoln.86xy], given that
[FLINK-32000|https://issues.apache.org/jira/browse/FLINK-32000] has been
resolved, we can close this issue now.
was (Author: zhanghao chen):
Hi [~zlzhang0122][~lincoln.86xy], given that
[FLINK-32000](https://issues.apache.org/jira/browse/FLINK-32000) has been
resolved, we can close this issue now.
> Show the maximum parallelism (number of key groups) of a job in Web UI
> ----------------------------------------------------------------------
>
> Key: FLINK-25068
> URL: https://issues.apache.org/jira/browse/FLINK-25068
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Affects Versions: 1.14.0
> Reporter: zlzhang0122
> Assignee: zlzhang0122
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.20.0
>
>
> Now, Flink use maximum parallelism as the number of key groups to distribute
> the key, the maximum parallelism can be set manually, or flink will set-up
> automatically, sometimes the value is useful and we may want to know it,
> maybe we can expose in the Web UI.
> By doing this, we can easily know the max parallelism we can suggest the user
> to scale when they are facing the leak of through-output, and we can know
> which subtask will processing the special value and we can find the log soon.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
