Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BEB77177C4 for ; Tue, 10 Feb 2015 21:39:20 +0000 (UTC) Received: (qmail 95617 invoked by uid 500); 10 Feb 2015 21:39:14 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 95557 invoked by uid 500); 10 Feb 2015 21:39:14 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 95543 invoked by uid 99); 10 Feb 2015 21:39:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 21:39:14 +0000 Date: Tue, 10 Feb 2015 21:39:14 +0000 (UTC) From: "Craig Welch (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-3966) Add separate cache for CompletedJobs with tasks loaded and without tasks loaded in JobHIstoryServer 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/MAPREDUCE-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314987#comment-14314987 ] Craig Welch commented on MAPREDUCE-3966: ---------------------------------------- Hmm, I actually thing we would be better off pulling out all of this complex storage / caching logic and defer that to a general purpose database layer, as suggested here: https://issues.apache.org/jira/browse/MAPREDUCE-3973?focusedCommentId=13226450&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13226450 > Add separate cache for CompletedJobs with tasks loaded and without tasks loaded in JobHIstoryServer > --------------------------------------------------------------------------------------------------- > > Key: MAPREDUCE-3966 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3966 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: jobhistoryserver, mrv2 > Affects Versions: 0.23.1 > Reporter: Vinod Kumar Vavilapalli > > After MAPREDUCE-3901, we should have separate caches for list of CompletedJob with tasks loaded and list of CompletedJob without tasks loaded. Once we have separate cache, we should increase the cache size for the list which doesn't load tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)