Paris Carbone created FLINK-1686:
------------------------------------
Summary: Streaming iteration heads cannot be instantiated
Key: FLINK-1686
URL: https://issues.apache.org/jira/browse/FLINK-1686
Project: Flink
Issue Type: Bug
Components: Streaming
Reporter: Paris Carbone
Priority: Critical
It looks that streaming jobs with iterations and dop > 1 do not work currently.
From what I see, when the TaskManager tries to instantiate a new
RuntimeEnvironment for the iteration head tasks it fails since the following
exception is being thrown:
java.lang.Exception: Failed to deploy the task Map (2/8) - execution #0 to slot
SimpleSlot (0)(1) - 0e39fcabcab3e8543cc2d8320f9de783 - ALLOCATED/ALIVE:
java.lang.Exception: Error setting up runtime environment:
java.lang.RuntimeException: Could not register the given element, broker slot
is already occupied.
at
org.apache.flink.runtime.execution.RuntimeEnvironment.<init>(RuntimeEnvironment.java:174)
at
org.apache.flink.runtime.taskmanager.TaskManager.org$apache$flink$runtime$taskmanager$TaskManager$$submitTask(TaskManager.scala:432)
.....
.....
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Could not
register the given element, broker slot is already occupied.
at
org.apache.flink.streaming.api.streamvertex.StreamIterationHead.setInputsOutputs(StreamIterationHead.java:64)
at
org.apache.flink.streaming.api.streamvertex.StreamVertex.registerInputOutput(StreamVertex.java:86)
at
org.apache.flink.runtime.execution.RuntimeEnvironment.<init>(RuntimeEnvironment.java:171)
... 20 more
Caused by: java.lang.RuntimeException: Could not register the given element,
broker slot is already occupied.
at
org.apache.flink.runtime.iterative.concurrent.Broker.handIn(Broker.java:39)
at
org.apache.flink.streaming.api.streamvertex.StreamIterationHead.setInputsOutputs(StreamIterationHead.java:62)
The IterateTest passed since it is using a dop of 1 but for higher parallelism
it fails. Also, the IterateExample fails as well if you try to run it.
I will debug this once I find some time so any ideas of what could possible
cause this are more than welcome.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
