You need to better manage the colocation of the mapreduce runtime. In other
words, you are allowing mapreduce to grab too many node resources,
resulting in activation of the kernel's OOM killer. A good rule of thumb is
the aggregate of all Java heaps (daemons like DataNOde, RegionServer,
NodeManager, etc. + the max allowed number of mapreduce jobs * task heap
setting). Reduce the allowed mapreduce task concurrency.
On Tue, Jul 22, 2014 at 8:15 AM, Tianying Chang <[EMAIL PROTECTED]> wrote:
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

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