Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # user >> Externalizing Hadoop configuration files


Copy link to this message
-
Re: Externalizing Hadoop configuration files

See also https://issues.apache.org/jira/browse/HADOOP-5670 .
On Feb 16, 2011, at 3:32 PM, Ted Yu wrote:

> You need to develop externalization yourself.
>
> Our installer uses place holders such as:
> <property>
>  <name>fs.checkpoint.dir</name>
>
> <value>dataFolderPlaceHolder/dfs/namesecondary,backupFolderPlaceHolder/namesecondary</value>
>
> They would be resolved at time of deployment.
>
> On Wed, Feb 16, 2011 at 3:06 PM, Jing Zang <[EMAIL PROTECTED]>wrote:
>
>>
>> How do I externalize the parameters in hadoop configuration files so make
>> it easier for the operations team?. Ideally something like:
>> File: mapred-site.xml
>> <property>        <name>mapred.job.tracker</name>
>> <value>${hadoop.mapred}</value>    </property>
>> File: hadoop.conf (External to the app)hadoop.mapred=hadoop:9001
>> Anything as easy as Spring' sPropertyPlaceholderConfigurer or similar? How
>> do you guys externalize the parameters to a configuration file outside the
>> app?
>> Thanks.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB