[
https://issues.apache.org/jira/browse/FLINK-30917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688303#comment-17688303
]
Lijie Wang commented on FLINK-30917:
------------------------------------
master: b3998324b685afc779954f7e54cc0d8f281267ec
release-1.17 : e1c6352d18a19403e3eb80736c58b842de21bc88
> 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)
