[
https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450242#comment-17450242
]
zlzhang0122 commented on FLINK-25068:
-------------------------------------
[~Zhanghao Chen] Same as what i thought! We can add the max parallelism just
under the job parallelism, name as job max parallelism.etc, and the implemetion
is easy since we can add an attribute in JobConfigInfo and
ArchivedExecutionConfig. [~trohrmann] [~chesnay] [~sewen] what do you think? If
this implemetion has no problem, I can create a pr for this.
> 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
> Priority: Major
>
> 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.1#820001)
