[jira] [Commented] (HIVE-13002) Hive object is not thread safe, is shared via a threadlocal and thus should not be passed around too much - part 1

["Ashutosh Chauhan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172959#comment-15172959 ] 

Ashutosh Chauhan commented on HIVE-13002:
-----------------------------------------

Patch looks good. Failures need to be looked at. 
Do we know how perf logger was getting shared across threads? Which class was culprit for caching it?

> Hive object is not thread safe, is shared via a threadlocal and thus should not be passed around too much - part 1
> ------------------------------------------------------------------------------------------------------------------
>
>                 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.02.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)