flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2942) Dangling operators in web UI's program visualization (non-deterministic)
Date Fri, 30 Oct 2015 15:48:27 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982730#comment-14982730

Maximilian Michels commented on FLINK-2942:

Thanks for for reporting this with attached screenshots!

> Dangling operators in web UI's program visualization (non-deterministic)
> ------------------------------------------------------------------------
>                 Key: FLINK-2942
>                 URL: https://issues.apache.org/jira/browse/FLINK-2942
>             Project: Flink
>          Issue Type: Bug
>          Components: Webfrontend
>    Affects Versions: 0.10
>         Environment: OSX, Firefox and Chrome
>            Reporter: Fabian Hueske
>            Priority: Critical
>             Fix For: 0.10, 1.0
>         Attachments: Screen Shot 2015-10-29 at 17.11.19.png, Screen Shot 2015-10-29 at
20.51.46.png, Screen Shot 2015-10-29 at 20.52.13.png
> When visualizing a program with three {{MapPartition}} operators that branch off from
an {{OuterJoin}} operator, two of the three {{MapPartition}} operators are not connected to
the {{OuterJoin}} operator and appear to have no input.
> The problem is present in FireFox as well as in Chrome. I'll attach a screenshot.
> The problem and be reproduced by executing the "Cascading for the impatient" [TFIDF example
program|https://github.com/Cascading/Impatient/tree/master/part5] using the [Cascading Flink
> Update: It appears that the problem is non-deterministic. I ran the same job again (same
setup) and the previously missing connections were visualized. However, the UI showed only
one input for a binary operator (OuterJoin). Running the job a third time resulted in a graph
layout which was again different from both runs before. However, two of the {{MapPartition}}
operators had not inputs just as in the first run.

This message was sent by Atlassian JIRA

View raw message