[
https://issues.apache.org/jira/browse/FLINK-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304061#comment-17304061
]
Till Rohrmann commented on FLINK-21844:
---------------------------------------
I see the problem and I agree that this is confusing for our users.
Looking at the code, it seems that we set the max parallelism to 128 if neither
parallelism nor max parallelism has been configured. I am wondering whether
this value would be too low for some users who will try out the reactive mode.
> 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
> Priority: Major
>
> 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)
