Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
MapReduce >> mail # user >> OOM/crashes due to process number limit

Aiden Bell 2012-10-18, 14:24
谢良 2012-10-19, 04:10
Aiden Bell 2012-10-19, 11:04
Copy link to this message
答复: 答复: OOM/crashes due to process number limit
A threadump should give you some clue on which kind of thread number is not expected,  hope it helpful for u
发件人: Aiden Bell [[EMAIL PROTECTED]]
发送时间: 2012年10月19日 19:04
主题: Re: 答复: OOM/crashes due to process number limit

Yep, and then the entire OS can't fork new processes.

On 19 October 2012 05:10, 谢良 <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
what's the exactly OOM error message, is it sth like "OutOfMemoryError: unable to create new native thread" ?
发件人: Aiden Bell [[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>]
发送时间: 2012年10月18日 22:24
主题: OOM/crashes due to process number limit

Hi All,

Im running quite a basic map/reduce job with 10 or so map tasks. During the task's execution, the
entire stack (and my OS for that matter) start failing due to being unable to fork() new processes.
It seems Hadoop (1.0.3) is creating 700+ threads and exhausting this resource. RAM utilisation is fine however.
This still occurs with ulimit set to unlimited.

Any ideas or advice would be great, it seems very sketchy for a task that doesn't require much grunt.

Never send sensitive or private information via email unless it is encrypted. http://www.gnupg.org