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 4212118D82 for ; Fri, 26 Feb 2016 21:28:19 +0000 (UTC) Received: (qmail 36864 invoked by uid 500); 26 Feb 2016 21:28:18 -0000 Delivered-To: apmail-hive-issues-archive@hive.apache.org Received: (qmail 36749 invoked by uid 500); 26 Feb 2016 21:28:18 -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 36570 invoked by uid 99); 26 Feb 2016 21:28:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Feb 2016 21:28:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7A0092C14E1 for ; Fri, 26 Feb 2016 21:28:18 +0000 (UTC) Date: Fri, 26 Feb 2016 21:28:18 +0000 (UTC) From: "Ashutosh Chauhan (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-13002) metastore call timing is not threadsafe 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-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169856#comment-15169856 ] Ashutosh Chauhan commented on HIVE-13002: ----------------------------------------- I dont think we really have a choice to ignore root cause. Its better to fix caching of ThreadLocal Hive variable. Performance (of access via Hive.get()) can't get in a way of correctness. > metastore call timing is not threadsafe > --------------------------------------- > > Key: HIVE-13002 > URL: https://issues.apache.org/jira/browse/HIVE-13002 > Project: Hive > Issue Type: Bug > Reporter: Sergey Shelukhin > Assignee: Sergey Shelukhin > Attachments: HIVE-13002.01.patch, HIVE-13002.patch > > > Discovered in some q test run: > {noformat} > TestCliDriver.testCliDriver_insert_values_orig_table:123->runTest:199 Unexpected exception java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926) > at java.util.HashMap$EntryIterator.next(HashMap.java:966) > at java.util.HashMap$EntryIterator.next(HashMap.java:964) > at org.apache.hadoop.hive.ql.metadata.Hive.dumpAndClearMetaCallTiming(Hive.java:3412) > at org.apache.hadoop.hive.ql.Driver.dumpMetaCallTimingWithoutEx(Driver.java:574) > at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1722) > at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1342) > at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1113) > at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1101) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)