[
https://issues.apache.org/jira/browse/FLINK-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304094#comment-17304094
]
Chesnay Schepler commented on FLINK-21844:
------------------------------------------
There's been a recent discussion in FLINK-21695 about raising the default
maxParallelism and handling the associated migration/compatibility/performance
concerns.
I think we should just stick to the current defaults (128) for now and document
it accordingly that users may want to increase this.
> 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)
