Fabian Hueske created FLINK-4688:
------------------------------------
Summary: 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: Optimizer
Affects Versions: 1.2.0, 1.1.3
Reporter: Fabian Hueske
When optimizing a plan with many operators (more than 250), the optimizer gets
stuck for hours.
A user reported this problem on the user@f.a.o 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
(v6.3.4#6332)
