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 >> Which config parameters are node-specific?


Copy link to this message
-
Re: Which config parameters are node-specific?
I believe all these parameters can be set as node-specific, because they are
in different JVM.
Correct me if I am wrong.

On Wed, Jan 20, 2010 at 8:31 AM, Zhang, Zhang <[EMAIL PROTECTED]>wrote:

>
> Where do I find information about which config parameters can be set as
> per-node property, and which ones apply to all nodes? For example, I have a
> cluster consisting of two classes of nodes. One class is dual-core 4GB
> memory nodes, and the other class is 16-core 128GB memory nodes. It
> certainly makes sense to configure them differently. So the questions is,
> which parameters I should pay attention to? I vaguely know that probably at
> least the following ones can be set as node-specific:
>
>    mapred.tasktracker.map.tasks.maximum
>    mapred.tasktracker.reduce.tasks.maximum
>
>
> But anything beyond that? How about the following ones, can I set them as
> node-specific parameters?
>
>    mapred.child.java.opts
>    tasktracker.http.threads
>    dfs.datanode.handler.count
>    io.sort.factor
>    io.sort.mb
>    mapred.inmem.merge.threshold
>    mapred.job.reduce.input.buffer.percent
>
>
> Thanks!
>
> Zhang
>
>
--
Best Regards

Jeff Zhang
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