[
https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450809#comment-17450809
]
zlzhang0122 edited comment on FLINK-25068 at 11/30/21, 2:31 AM:
----------------------------------------------------------------
[~trohrmann] Nice advice!!! +1 for expose on a per operator basis. I think we
can put it in the Job Overview - Job Graph, just under the Parallelism and also
in the Job Detail tab.
was (Author: zlzhang0122):
[~trohrmann] Nice advice!!! +1 for expose maximum parallelism on a per
operator basis. I think we can put it in the Job Overview - Job Graph, just
under the Parallelism and also in the Job Detail tab.
> 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)
