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
MapReduce >> mail # dev >> JVM vs container memory configs


Copy link to this message
-
Re: JVM vs container memory configs
Radim,

Those are already present - the discussion is about the heap vs.
requested memory resource.

On Sun, May 5, 2013 at 3:22 AM, Radim Kolar <[EMAIL PROTECTED]> wrote:
>
> While looking into MAPREDUCE-5207 (adding defaults for
> mapreduce.{map|reduce}.memory.mb), I was wondering how much headroom
> should be left on top of mapred.child.java.opts (or other similar JVM opts)
> for
> the container memory itself?
>
> I would like to have separated java option settings for map/reduce parts.
> Something like
> mapred.map.child.java.opts mapred.reduce.child.java.opts.
>

--
Harsh J
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