You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2014/10/24 06:21:33 UTC

[jira] [Created] (HADOOP-11223) Offer a read-only conf alternative to new Configuration()

Gopal V created HADOOP-11223:
--------------------------------

             Summary: 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
            Reporter: Gopal V


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)