Yep I saw the same thing. You can either change that settings up your maximum heap size to, say, 128MB. (Add -Xmx128m to the command line.) I just committed a change to build.xml to address this. Otherwise the JVM default is something like 64MB. It's not that your computer is out of memory.
Yes it just looks like the new default settings assume more memory. It can be tuned but it seems like 128MB seems like an OK amount of memory for a worker to use. Sean On Mon, Jun 2, 2008 at 8:55 AM, Grant Ingersoll <[EMAIL PROTECTED]> wrote: > I'm getting the same errors upon upgrading. We should look at the Hadoop 17 > changes. > > On Jun 2, 2008, at 5:50 AM, deneche abdelhakim wrote: > >> I checked the last version of Mahout (rev. 662372) and got the following >> exception with many tests (the list of this tests is at the end of this >> post): >> >> java.io.IOException: Job failed! >> >> the following message is printed in System.err : >> >> java.lang.OutOfMemoryError: Java heap space >> >> I think its somehow caused by using Hadoop 0.17.0 as my own tests run >> perfectly with Hadoop 0.16.4 >> >> here are the tests that don't pass >> >> org.apache.mahout.clustering.canopy.TestCanopyCreation: >> testCanopyGenManhattanMR >> testCanopyGenEuclideanMR >> testClusteringManhattanMR >> testClusteringEuclideanMR >> testClusteringManhattanMRWithPayload >> testClusteringEuclideanMRWithPayload >> testUserDefinedDistanceMeasure >> >> org.apache.mahout.clustering.meanshift.TestMeanShift >> testCanopyEuclideanMRJob >> >> __________________________________________________ >> Do You Yahoo!? >> En finir avec le spam? Yahoo! Mail vous offre la meilleure protection >> possible contre les messages non sollicités >> http://mail.yahoo.fr Yahoo! Mail > > -------------------------- > Grant Ingersoll > http://www.lucidimagination.com > > >
