flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Kruse (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-1754) Deadlock in job execution
Date Thu, 19 Mar 2015 17:59:39 GMT
Sebastian Kruse created FLINK-1754:
--------------------------------------

             Summary: Deadlock in job execution
                 Key: FLINK-1754
                 URL: https://issues.apache.org/jira/browse/FLINK-1754
             Project: Flink
          Issue Type: Bug
            Reporter: Sebastian Kruse


I have encountered a reproducible deadlock in the execution of one of my jobs. The part of
the plan, where this happens, is the following:
{code:java}
    /** Performs the reduction via creating transitive INDs and removing them from the original
IND set. */
    private DataSet<Tuple2<Integer, int[]>> calculateTransitiveReduction1(DataSet<Tuple2<Integer,
int[]>> inclusionDependencies) {
        // Concatenate INDs (only one hop).
        DataSet<Tuple2<Integer, int[]>> transitiveInds = inclusionDependencies
                .flatMap(new SplitInds())
                .joinWithTiny(inclusionDependencies)
                .where(1).equalTo(0)
                .with(new ConcatenateInds());

        // Remove the concatenated INDs to come up with a transitive reduction of the INDs.
        return inclusionDependencies
                .coGroup(transitiveInds)
                .where(0).equalTo(0)
                .with(new RemoveTransitiveInds());
    }
{code}
Seemingly, the flatmap operator waits infinitely for a free buffer to write on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message