[
https://issues.apache.org/jira/browse/FLINK-13707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329490#comment-17329490
]
Flink Jira Bot commented on FLINK-13707:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Make max parallelism configurable
> ----------------------------------
>
> Key: FLINK-13707
> URL: https://issues.apache.org/jira/browse/FLINK-13707
> Project: Flink
> Issue Type: New Feature
> Components: API / DataStream
> Reporter: xuekang
> Assignee: xuekang
> Priority: Minor
> Labels: stale-assigned, stale-minor
>
> For now, if a user set parallelism larger than 128, and does not set max
> parallelism explicitly, the system will compute a max parallelism, which is
> 1.5 * parallelism. When the job changes the parallelism and recover from a
> savepoint, there may be some problem when restoring states from the
> savepoint, as the number of key groups changed.
> To avoid this problem, and trying not to modify the code of existing jobs,
> we want to configure the default max parallelism in flink-conf.yaml, but it
> is not configurable now.
> Should we make it configurable? Any comments would be appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
