Brian, Could it be your OS that's running out of some resources, and not the JVM? How many processes/tasks do you see in top? Do you see any swap there?
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Brian Whitman <br...@echonest.com> > To: solr-user@lucene.apache.org > Sent: Friday, January 2, 2009 10:52:59 AM > Subject: cannot allocate memory for snapshooter > > I have an indexing machine on a test server (a mid-level EC2 instance, 8GB > of RAM) and I run jetty like: > > java -server -Xms5g -Xmx5g -XX:MaxPermSize=128m > -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/heap > -Dsolr.solr.home=/vol/solr -Djava.awt.headless=true -jar start.jar > > The indexing master is set to snapshoot on commit. Sometimes (not always) > the snapshot fails with > > SEVERE: java.io.IOException: Cannot run program "/vol/solr/bin/snapshooter": > java.io.IOException: error=12, Cannot allocate memory > at java.lang.ProcessBuilder.start(Unknown Source) > > Why would snapshooter need more than 2GB ram? /proc/meminfo says (with solr > running & nothing else) > > MemTotal: 7872040 kB > MemFree: 2018404 kB > Buffers: 67704 kB > Cached: 2161880 kB > SwapCached: 0 kB > Active: 3446348 kB > Inactive: 2186964 kB > SwapTotal: 0 kB > SwapFree: 0 kB > Dirty: 8 kB > Writeback: 0 kB > AnonPages: 3403728 kB > Mapped: 12016 kB > Slab: 37804 kB > SReclaimable: 20048 kB > SUnreclaim: 17756 kB > PageTables: 7476 kB > NFS_Unstable: 0 kB > Bounce: 0 kB > CommitLimit: 3936020 kB > Committed_AS: 5383624 kB > VmallocTotal: 34359738367 kB > VmallocUsed: 340 kB > VmallocChunk: 34359738027 kB
