Re: test-patch failing with OOM errors in javah

2013-10-31 Thread Jason Lowe
I don't think that OOM error below indicates it needs more heap space, as it's complaining about the ability to create a new native thread. That usually is caused by lack of available virtual address space or hitting process ulimits. What's most likely going on is the jenkins user is hitting

test-patch failing with OOM errors in javah

2013-10-30 Thread Alejandro Abdelnur
The following is happening in builds for MAPREDUCE and YARN patches. I've seen the failures in hadoop5 and hadoop7 machines. I've increased Maven memory to 1GB (export MAVEN_OPTS=-Xmx1024m in the jenkins jobs) but still some failures persist:

Re: test-patch failing with OOM errors in javah

2013-10-30 Thread Roman Shaposhnik
I can take a look sometime later today. Meantime I can only say that I've been running into 1Gb limit in a few builds as of late. These days -- I just go with 2G by default. Thanks, Roman. On Wed, Oct 30, 2013 at 3:33 PM, Alejandro Abdelnur t...@cloudera.com wrote: The following is happening in

Re: test-patch failing with OOM errors in javah

2013-10-30 Thread Omkar Joshi
yes even I do the same.. I just use this to build export _JAVA_OPTIONS=-Djava.awt.headless=true -Xmx2048m -Xms2048m mvn clean install package -Pdist -Dtar -DskipTests -Dmaven.javadoc.skip=true Thanks, Omkar Joshi *Hortonworks Inc.* http://www.hortonworks.com On Wed, Oct 30, 2013 at 3:39 PM,