[
https://issues.apache.org/jira/browse/FLINK-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306047#comment-17306047
]
Till Rohrmann commented on FLINK-21844:
---------------------------------------
I think if the user does not configure an explicit {{maxParallelism}}, then
Flink should fall back to the default setting as defined in
https://github.com/apache/flink/blob/37a8e3cac73587fb845617c6accd1c51def306e6/flink-runtime/src/main/java/org/apache/flink/runtime/state/KeyGroupRangeAssignment.java#L137.
But we shouldn't fail since we did not fail before.
> Do not auto-configure maxParallelism when setting "scheduler-mode: reactive"
> ----------------------------------------------------------------------------
>
> Key: FLINK-21844
> URL: https://issues.apache.org/jira/browse/FLINK-21844
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Konstantin Knauf
> Assignee: Austin Cawley-Edwards
> Priority: Major
> Fix For: 1.13.0
>
>
> I believe we should not automatically change the maxParallelism when the
> "scheduler-mode" is set to "reactive", because:
> * it magically breaks savepoint compatibility, when you switch between
> default and reactive scheduler mode
> * the maximum parallelism is an orthogonal concern that in my opinion should
> not be mixed with the scheduler mode. The reactive scheduler should respect
> the maxParallelism, but it should not set/ change its default value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
