[
https://issues.apache.org/jira/browse/FLINK-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328895#comment-17328895
]
Flink Jira Bot commented on FLINK-4688:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Optimizer hangs for hours when optimizing complex plans
> -------------------------------------------------------
>
> Key: FLINK-4688
> URL: https://issues.apache.org/jira/browse/FLINK-4688
> Project: Flink
> Issue Type: Bug
> Components: API / DataSet
> Affects Versions: 1.1.3, 1.2.0
> Reporter: Fabian Hueske
> Priority: Major
> Labels: stale-major
> Attachments: stacktrace_32minsAfterSubmission.java,
> stacktrace_76minsAfterSubmission.java, stacktrace_shortlyAfterSubmission.java
>
>
> When optimizing a plan with many operators (more than 250), the optimizer
> gets stuck for hours.
> A user reported this problem on the [email protected] list [1] and provided
> stacktraces taken at different points in time (shortly after submission, 32
> minutes and 76 minutes after submission) (see attachments).
> The stacktraces show deeply recursive {{hasDamOnPathDownTo()}} calls. Maybe
> it is possible to improve the performance by caching the results?
> [1]
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Complex-batch-workflow-needs-too-much-time-to-create-executionPlan-tp8596.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
