Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 71EABED0B for ; Sun, 17 Feb 2013 18:23:13 +0000 (UTC) Received: (qmail 83852 invoked by uid 500); 17 Feb 2013 18:23:12 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 83798 invoked by uid 500); 17 Feb 2013 18:23:12 -0000 Mailing-List: contact dev-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 dev@hive.apache.org Received: (qmail 83787 invoked by uid 500); 17 Feb 2013 18:23:12 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 83784 invoked by uid 99); 17 Feb 2013 18:23:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Feb 2013 18:23:12 +0000 Date: Sun, 17 Feb 2013 18:23:12 +0000 (UTC) From: "Ashutosh Chauhan (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-4000) Hive client goes into infinite loop at 100% cpu 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-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580241#comment-13580241 ] Ashutosh Chauhan commented on HIVE-4000: ---------------------------------------- +1 > 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