hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Commented] (HIVE-11165) Calcite planner might have a thread-safety issue compiling in parallel
Date Thu, 09 Jul 2015 21:07:04 GMT


Sergey Shelukhin commented on HIVE-11165:

I have seen the following callstack that may be related, after ctrl-c-ing HiveServer2 that
was stuck forever
Exception in thread "HiveServer2-Handler-Pool: Thread-81" java.lang.OutOfMemoryError: GC overhead
limit exceeded
   at java.util.HashMap.resize(
   at java.util.HashMap.putVal(
   at java.util.HashMap.put(
   at java.util.HashSet.add(
   at org.apache.calcite.util.graph.BreadthFirstIterator.reachable(
   at org.apache.calcite.plan.hep.HepPlanner.collectGarbage(
   at org.apache.calcite.plan.hep.HepPlanner.getGraphIterator(
   at org.apache.calcite.plan.hep.HepPlanner.applyRules(
   at org.apache.calcite.plan.hep.HepPlanner.executeInstruction(
   at org.apache.calcite.plan.hep.HepInstruction$RuleCollection.execute(
   at org.apache.calcite.plan.hep.HepPlanner.executeProgram(
   at org.apache.calcite.plan.hep.HepPlanner.findBestExp(
   at org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.hepPlan(
   at org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.applyPreJoinOrderingTransforms(

> Calcite planner might have a thread-safety issue compiling in parallel
> ----------------------------------------------------------------------
>                 Key: HIVE-11165
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: CBO
>    Affects Versions: 2.0.0
>            Reporter: Gopal V
>         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

View raw message