[ https://issues.apache.org/jira/browse/FLINK-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xingcan Cui resolved FLINK-9289. -------------------------------- Resolution: Fixed Fix Version/s: 1.7.0 1.6.1 1.5.3 1.4.3 Fixed in 1.4 c9d6607b017f871e292650caab3802175a5b7b4a Fixed in 1.5 9f1c12c10c3eb7b302f0688ed1b60fd08942dc03 Fixed in 1.6 f7501a44a3d8319e3be3996fa5ee4130589c0784 Fixed in 1.7 7af933b78400921ae798b8a882cba8ecff5c94be > Parallelism of generated operators should have max parallism of input > --------------------------------------------------------------------- > > Key: FLINK-9289 > URL: https://issues.apache.org/jira/browse/FLINK-9289 > Project: Flink > Issue Type: Bug > Components: DataSet API > Affects Versions: 1.4.2, 1.5.2, 1.6.0 > Reporter: Fabian Hueske > Assignee: Xingcan Cui > Priority: Major > Labels: pull-request-available > Fix For: 1.4.3, 1.5.3, 1.6.1, 1.7.0 > > > The DataSet API aims to chain generated operators such as key extraction > mappers to their predecessor. This is done by assigning the same parallelism > as the input operator. > If a generated operator has more than two inputs, the operator cannot be > chained anymore and the operator is generated with default parallelism. This > can lead to a {code}NoResourceAvailableException: Not enough free slots > available to run the job.{code} as reported by a user on the mailing list: > https://lists.apache.org/thread.html/60a8bffcce54717b6273bf3de0f43f1940fbb711590f4b90cd666c9a@%3Cuser.flink.apache.org%3E > I suggest to set the parallelism of a generated operator to the max > parallelism of all of its inputs to fix this problem. > Until the problem is fixed, a workaround is to set the default parallelism at > the {{ExecutionEnvironment}}: > {code} > ExecutionEnvironment env = ... > env.setParallelism(2); > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)