Return-Path: X-Original-To: apmail-hive-issues-archive@minotaur.apache.org Delivered-To: apmail-hive-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 09F3B18E44 for ; Thu, 9 Jul 2015 21:07:05 +0000 (UTC) Received: (qmail 90893 invoked by uid 500); 9 Jul 2015 21:07:05 -0000 Delivered-To: apmail-hive-issues-archive@hive.apache.org Received: (qmail 90868 invoked by uid 500); 9 Jul 2015 21:07:04 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 90858 invoked by uid 99); 9 Jul 2015 21:07:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jul 2015 21:07:04 +0000 Date: Thu, 9 Jul 2015 21:07:04 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-11165) Calcite planner might have a thread-safety issue compiling in parallel MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-11165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621262#comment-14621262 ] 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 {noformat} Exception in thread "HiveServer2-Handler-Pool: Thread-81" java.lang.OutOfMemoryError: GC overhead limit exceeded at java.util.HashMap.resize(HashMap.java:703) at java.util.HashMap.putVal(HashMap.java:662) at java.util.HashMap.put(HashMap.java:611) at java.util.HashSet.add(HashSet.java:219) at org.apache.calcite.util.graph.BreadthFirstIterator.reachable(BreadthFirstIterator.java:61) at org.apache.calcite.plan.hep.HepPlanner.collectGarbage(HepPlanner.java:900) at org.apache.calcite.plan.hep.HepPlanner.getGraphIterator(HepPlanner.java:427) at org.apache.calcite.plan.hep.HepPlanner.applyRules(HepPlanner.java:400) at org.apache.calcite.plan.hep.HepPlanner.executeInstruction(HepPlanner.java:285) at org.apache.calcite.plan.hep.HepInstruction$RuleCollection.execute(HepInstruction.java:72) at org.apache.calcite.plan.hep.HepPlanner.executeProgram(HepPlanner.java:207) at org.apache.calcite.plan.hep.HepPlanner.findBestExp(HepPlanner.java:194) at org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.hepPlan(CalcitePlanner.java:1035) at org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.applyPreJoinOrderingTransforms(CalcitePlanner.java:964) ... {noformat} > 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 > 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)