[
https://issues.apache.org/jira/browse/HIVE-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580396#comment-13580396
]
Hudson commented on HIVE-4000:
------------------------------
Integrated in hive-trunk-hadoop1 #87 (See
[https://builds.apache.org/job/hive-trunk-hadoop1/87/])
HIVE-4000 Hive client goes into infinite loop at 100% cpu (Owen Omalley via
Ashutosh Chauhan) (Revision 1447122)
Result = ABORTED
hashutosh :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1447122
Files :
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/QueryPlan.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/history/HiveHistory.java
*
/hive/trunk/serde/src/java/org/apache/hadoop/hive/serde2/typeinfo/TypeInfoUtils.java
> Hive client goes into infinite loop at 100% cpu
> -----------------------------------------------
>
> Key: HIVE-4000
> URL: https://issues.apache.org/jira/browse/HIVE-4000
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.11.0
>
> Attachments: HIVE-4000.D8493.1.patch, HIVE-4000.D8493.2.patch
>
>
> The Hive client starts multiple threads to track the progress of the
> MapReduce jobs. Unfortunately those threads access several static HashMaps
> that are not protected by locks. When the HashMaps are modified, they
> sometimes cause race conditions that lead to the client threads getting stuck
> in infinite loops.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
