[jira] [Updated] (FLINK-30917) The user configured max parallelism does not take effect when using adaptive batch scheduler

2023-02-14 Thread Lijie Wang (Jira)


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

Lijie Wang updated FLINK-30917:
---
Fix Version/s: 1.16.2

> The user configured max parallelism does not take effect when using adaptive 
> batch scheduler
> 
>
> Key: FLINK-30917
> URL: https://issues.apache.org/jira/browse/FLINK-30917
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Coordination
>Affects Versions: 1.17.0, 1.16.1
>Reporter: Lijie Wang
>Assignee: Lijie Wang
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.17.0, 1.16.2
>
>
> Currently, the adaptive batch scheduler only respects the global maximum 
> parallelism(which is configured by option {{parallelism.default}} or 
> {{execution.batch.adaptive.auto-parallelism.max-parallelism}}, see 
> FLINK-30686 for details) when deciding parallelism for job vertices, the 
> maximum parallelism of vertices configured by the user through 
> {{setMaxParallelism}} will not be respected.
> In this ticket, we will change the behavior so that the user-configured max 
> parallelism also be respected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-30917) The user configured max parallelism does not take effect when using adaptive batch scheduler

2023-02-08 Thread Zhu Zhu (Jira)


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

Zhu Zhu updated FLINK-30917:

Affects Version/s: 1.16.1
   1.17.0

> The user configured max parallelism does not take effect when using adaptive 
> batch scheduler
> 
>
> Key: FLINK-30917
> URL: https://issues.apache.org/jira/browse/FLINK-30917
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Coordination
>Affects Versions: 1.17.0, 1.16.1
>Reporter: Lijie Wang
>Assignee: Lijie Wang
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.17.0
>
>
> Currently, the adaptive batch scheduler only respects the global maximum 
> parallelism(which is configured by option {{parallelism.default}} or 
> {{execution.batch.adaptive.auto-parallelism.max-parallelism}}, see 
> FLINK-30686 for details) when deciding parallelism for job vertices, the 
> maximum parallelism of vertices configured by the user through 
> {{setMaxParallelism}} will not be respected.
> In this ticket, we will change the behavior so that the user-configured max 
> parallelism also be respected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-30917) The user configured max parallelism does not take effect when using adaptive batch scheduler

2023-02-06 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated FLINK-30917:
---
Labels: pull-request-available  (was: )

> The user configured max parallelism does not take effect when using adaptive 
> batch scheduler
> 
>
> Key: FLINK-30917
> URL: https://issues.apache.org/jira/browse/FLINK-30917
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Coordination
>Reporter: Lijie Wang
>Assignee: Lijie Wang
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.17.0
>
>
> Currently, the adaptive batch scheduler only respects the global maximum 
> parallelism(which is configured by option {{parallelism.default}} or 
> {{execution.batch.adaptive.auto-parallelism.max-parallelism}}, see 
> FLINK-30686 for details) when deciding parallelism for job vertices, the 
> maximum parallelism of vertices configured by the user through 
> {{setMaxParallelism}} will not be respected.
> In this ticket, we will change the behavior so that the user-configured max 
> parallelism also be respected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)