[FLINK-5040] Set correct input channel types with eager scheduling

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.4, 1.2.0
• Component/s: Runtime / Coordination
• Assignee: Ufuk Celebi
• Reporter: Ufuk Celebi
• Created: 09/Nov/16 17:24
• Updated: 28/Feb/19 14:01
• Resolved: 11/Nov/16 09:00

Description

When we do eager deployment all intermediate stream/partition locations are already known when scheduling an intermediate stream/partition consumer. Nonetheless we saw tasks with "unknown input channels" that were updated lazily during runtime. This was caused by a wrong producer execution state check requiring the producers to be in RUNNING or DEPLOYING state when creating consumer input channels.

(We had a bogus fix for this in FLINK-3232. With that "fix" we actually did not fix anything correctly and instead doubled the number of schedule or update consumer messages we sent.)

Issue Links

• links to: GitHub Pull Request #2783
• links to: GitHub Pull Request #2784