[
https://issues.apache.org/jira/browse/FLINK-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834373#comment-15834373
]
ASF GitHub Bot commented on FLINK-5473:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/3182#discussion_r97293150
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/ExecutionJobVertex.java
---
@@ -230,9 +237,46 @@ public int getParallelism() {
return parallelism;
}
+ /**
+ * Returns the effective max parallelism. This value is determined in
the following order of priority:
+ * <p>
+ * (maxParallelismConfigured) overrides (maxParallelismOverride)
override (max(128, roundUp(parallelism)) / default)
--- End diff --
`maxParallelismOverride` => `maxParallelismDerived`?
> setMaxParallelism() higher than 1 is possible on non-parallel operators
> -----------------------------------------------------------------------
>
> Key: FLINK-5473
> URL: https://issues.apache.org/jira/browse/FLINK-5473
> Project: Flink
> Issue Type: Bug
> Components: DataStream API
> Affects Versions: 1.2.0
> Reporter: Robert Metzger
> Assignee: Stefan Richter
>
> While trying out Flink 1.2, I found out that you can set a maxParallelism
> higher than 1 on a non-parallel operator.
> I think we should have the same semantics as the setParallelism() method.
> Also, when setting a global maxParallelism in the execution environment, it
> will be set as a default value for the non-parallel operator.
> When restoring a savepoint from 1.1, you have to set the maxParallelism to
> the parallelism of the 1.1 job. Non-parallel operators will then also get the
> maxPar set to this value, leading to an error on restore.
> So currently, users restoring from 1.1 to 1.2 have to manually set the
> maxParallelism to 1 for all non-parallel operators.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
