Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 23 Feb 2012 03:03:51 +0000 (UTC)
From: "Siddharth Seth (Created) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1130464210.7949.1329966231860.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (MAPREDUCE-3901) lazy load JobHistory Task and
 TaskAttempt details
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

lazy load JobHistory Task and TaskAttempt details
-------------------------------------------------

                 Key: MAPREDUCE-3901
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3901
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
          Components: jobhistoryserver, mrv2
    Affects Versions: 0.23.0
            Reporter: Siddharth Seth
            Assignee: Siddharth Seth


The job history UI and MRClientProtocol calls routed via JobHistory are very slow for large jobs. Some of this time is spent parsing the history file. A good chunk is spent pre-creating lots of objects which may never be used. Those can be create when required - bringing down the load times of job history pages and getJobReport etc calls to approximately the history file parse time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira