Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <8826504.6031274245014113.JavaMail.jira@thor>
Date: Wed, 19 May 2010 00:56:54 -0400 (EDT)
From: "Dmytro Molkov (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Updated: (HIVE-1349) Do not pull counters of non initialized
 jobs
In-Reply-To: <606890.111981274208111469.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Molkov updated HIVE-1349:
--------------------------------

    Attachment: HIVE-1349.3.patch

OK. Have a look at Shims implementation, does this look right?
I will submit for tests right away. 

> Do not pull counters of non initialized jobs
> --------------------------------------------
>
>                 Key: HIVE-1349
>                 URL: https://issues.apache.org/jira/browse/HIVE-1349
>             Project: Hadoop Hive
>          Issue Type: Improvement
>            Reporter: Dmytro Molkov
>         Attachments: HIVE-1349.2.patch, HIVE-1349.3.patch, HIVE-1349.patch
>
>
> Right now hive client puts a lot of pressure on the jobtracker by pulling the counters of the job that has just been submitted and is in the process of initializing tasks.
> While the job initialized tasks and reads the splits file it is holding the JobInProgress lock. The getCounters method acquires a JobTracker lock and waits for the JobInProgress lock. Since the read of the file can  take a couple (a couple of tens of seconds) the job tracker is effectively blocked for that period of time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.