Return-Path: 
 <common-issues-return-76373-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-common-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 69A1017C5E
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Mon, 26 Jan 2015 21:42:36 +0000 (UTC)
Received: (qmail 65088 invoked by uid 500); 26 Jan 2015 21:42:35 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 65038 invoked by uid 500); 26 Jan 2015 21:42:35 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 65026 invoked by uid 99); 26 Jan 2015 21:42:35 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2015 21:42:35 +0000
Date: Mon, 26 Jan 2015 21:42:35 +0000 (UTC)
From: "Gopal V (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12750268.1414124492000.176754.1422308555619@Atlassian.JIRA>
In-Reply-To: <JIRA.12750268.1414124492000@Atlassian.JIRA>
References: <JIRA.12750268.1414124492000@Atlassian.JIRA>
 <JIRA.12750268.1414124492760@arcas>
Subject: [jira] [Commented] (HADOOP-11223) Offer a read-only conf
 alternative to new Configuration()
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/HADOOP-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292452#comment-14292452 ] 

Gopal V commented on HADOOP-11223:
----------------------------------

[~cmccabe]: Agree, the current patch doesn't fix anything.

The primary blockage I had trying to implement this is the expected behaviour of addDefaultResource(). The overlays set programmatically is somewhat easier to disable cleanly.

> Offer a read-only conf alternative to new Configuration()
> ---------------------------------------------------------
>
>                 Key: HADOOP-11223
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11223
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Gopal V
>            Assignee: Varun Saxena
>              Labels: Performance
>         Attachments: HADOOP-11223.001.patch
>
>
> new Configuration() is called from several static blocks across Hadoop.
> This is incredibly inefficient, since each one of those involves primarily XML parsing at a point where the JIT won't be triggered & interpreter mode is essentially forced on the JVM.
> The alternate solution would be to offer a {{Configuration::getDefault()}} alternative which disallows any modifications.
> At the very least, such a method would need to be called from 
> # org.apache.hadoop.io.nativeio.NativeIO::<clinit>()
> # org.apache.hadoop.security.SecurityUtil::<clinit>()
> # org.apache.hadoop.yarn.factory.providers.RecordFactoryProvider::<clinit>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)