[jira] [Comment Edited] (FLINK-25068) Show the maximum parallelism (number of key groups) of a job in Web UI
[ https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Comment Edited] (FLINK-25068) Show the maximum parallelism (number of key groups) of a job in Web UI
[ https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474408#comment-17474408 ] zlzhang0122 edited comment on FLINK-25068 at 1/12/22, 10:07 AM: Since the [FLink-12067|https://issues.apache.org/jira/browse/FLINK-12607] have been merged and the implemention can be more easily. [~trohrmann] Could you assign me the ticket? was (Author: zlzhang0122): Since the FLink-12067 have been merged and the implemention can be more easily. [~trohrmann] Could you assign me the ticket? > 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 > > 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)
[jira] [Comment Edited] (FLINK-25068) Show the maximum parallelism (number of key groups) of a job in Web UI
[ https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Comment Edited] (FLINK-25068) Show the maximum parallelism (number of key groups) of a job in Web UI
[ https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450242#comment-17450242 ] zlzhang0122 edited comment on FLINK-25068 at 11/29/21, 8:11 AM: [~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? Any suggestion is very appreciate! If this implemetion has no problem, I can create a pr for this. was (Author: zlzhang0122): [~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)
[jira] [Comment Edited] (FLINK-25068) Show the maximum parallelism (number of key groups) of a job in Web UI
[ https://issues.apache.org/jira/browse/FLINK-25068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17449837#comment-17449837 ] Zhanghao Chen edited comment on FLINK-25068 at 11/27/21, 1:45 PM: -- +1 for this feature. I think we can put it in the Job Overview - Configuration - Execution Configuration component of the web UI. was (Author: zhanghao chen): +1 for this feature > 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)
