You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Phabricator (JIRA)" <ji...@apache.org> on 2013/02/11 20:01:15 UTC

[jira] [Updated] (HIVE-4000) Hive client goes into infinite loop at 100% cpu

     [ 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.1.patch

omalley requested code review of "HIVE-4000 [jira] Hive client goes into infinite loop at 100% cpu".

Reviewers: JIRA

HIVE-4000 fix race condition in HashMap on Hive client

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.

TEST PLAN
  Test in the cluster with the query that was demonstrating the problem.

REVISION DETAIL
  https://reviews.facebook.net/D8493

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

MANAGE HERALD RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/20739/

To: JIRA, omalley

                
> 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
>
>
> 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