[
https://issues.apache.org/jira/browse/HIVE-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-4000:
------------------------------
Attachment: HIVE-4000.D8493.2.patch
omalley updated the revision "HIVE-4000 [jira] Hive client goes into infinite
loop at 100% cpu".
Fixed a couple of spots where the id was null and caused problems for
the hashmap.
Reviewers: ashutoshc, JIRA
REVISION DETAIL
https://reviews.facebook.net/D8493
CHANGE SINCE LAST DIFF
https://reviews.facebook.net/D8493?vs=27561&id=27903#toc
BRANCH
hive-4000
ARCANIST PROJECT
hive
AFFECTED FILES
ql/src/java/org/apache/hadoop/hive/ql/QueryPlan.java
ql/src/java/org/apache/hadoop/hive/ql/history/HiveHistory.java
serde/src/java/org/apache/hadoop/hive/serde2/typeinfo/TypeInfoUtils.java
To: JIRA, ashutoshc, omalley
Cc: brock
> 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.10.1
>
> 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
