[jira] [Updated] (FLINK-25068) Show the maximum parallelism (number of key groups) of a job in Web UI

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-25068:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issue is assigned but has not received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a comment updating the community on your progress.  If this issue is waiting on feedback, please consider this a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone else may work on it.


> 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.16.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.7#820007)