flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ufuk Celebi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-5040) Set correct input channel types with eager scheduling
Date Wed, 09 Nov 2016 17:24:59 GMT
Ufuk Celebi created FLINK-5040:

             Summary: Set correct input channel types with eager scheduling
                 Key: FLINK-5040
                 URL: https://issues.apache.org/jira/browse/FLINK-5040
             Project: Flink
          Issue Type: Bug
          Components: JobManager
            Reporter: Ufuk Celebi
            Assignee: Ufuk Celebi
             Fix For: 1.2.0, 1.1.4

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.)

This message was sent by Atlassian JIRA

View raw message