[
https://issues.apache.org/jira/browse/HIVE-11165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269751#comment-15269751
]
Julian Hyde commented on HIVE-11165:
------------------------------------
I don't have an update. It's not obviously a thread-safety issue; the graph
which is blowing up in that call stack is not shared between threads. More
likely, the planner is firing rules over and over again until the graph of
RelNodes gets really large. Thread-safety is one of several possible causes of
that.
> Calcite planner might have a thread-safety issue compiling in parallel
> ----------------------------------------------------------------------
>
> Key: HIVE-11165
> URL: https://issues.apache.org/jira/browse/HIVE-11165
> Project: Hive
> Issue Type: Bug
> Components: CBO
> Affects Versions: 2.0.0
> Reporter: Gopal V
> Assignee: Jesus Camacho Rodriguez
> Attachments: RunJar-2015-06-30.snapshot
>
>
> After about 6 minutes trying to plan a query, the HiveServer2 was killed to
> restore functionality to a test run.
> The HEP planner is stuck on a TopologicalOrder traversal and there were no
> queries being fed into the HiveServer2 after it got stuck.
> TPC-DS query13 was the query in question, at 4 way parallel, which triggered
> the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
