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 17AB710E5A for ; Mon, 16 Sep 2013 14:21:18 +0000 (UTC) Received: (qmail 60030 invoked by uid 500); 16 Sep 2013 14:21:01 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 59962 invoked by uid 500); 16 Sep 2013 14:20:57 -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 59916 invoked by uid 99); 16 Sep 2013 14:20:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Sep 2013 14:20:53 +0000 Date: Mon, 16 Sep 2013 14:20:53 +0000 (UTC) From: "Sandy Ryza (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-5487) In task processes, JobConf is unnecessarily loaded again in Limits 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-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768340#comment-13768340 ] Sandy Ryza commented on MAPREDUCE-5487: --------------------------------------- bq. Shouldn't Limits.init(job) be called after adding the mapred config as resource? This would diverge from the previous behavior, which uses a vanilla JobConf for loading the Limits constants. bq. Personally, I don't like constants that are not 'constants', that seems to be the case of these limits. Totally agree, though also think it should be a separate patch. > In task processes, JobConf is unnecessarily loaded again in Limits > ------------------------------------------------------------------ > > Key: MAPREDUCE-5487 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5487 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: performance, task > Affects Versions: 2.1.0-beta > Reporter: Sandy Ryza > Assignee: Sandy Ryza > Attachments: MAPREDUCE-5487-1.patch, MAPREDUCE-5487.patch > > > Limits statically loads a JobConf, which incurs costs of reading files from disk and parsing XML. The contents of this JobConf are identical to the one loaded by YarnChild (before adding job.xml as a resource). Allowing Limits to initialize with the JobConf loaded in YarnChild would reduce task startup time. -- 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