Well, that's one. OutOfMemoryErrors will stop things from happening for sure, the cure is to give the JVM more memory.
Additionally, multiple update of a doc with the same <uniqueKey> will replace the old copy with a new one, that might be what you're seeing. But get rid of the OOM first. Best Erick On Sun, Jul 14, 2013 at 2:40 PM, glumet <jan.bouch...@gmail.com> wrote: > When I look into the log, there is: > > SEVERE: auto commit error...:java.lang.IllegalStateException: this writer > hit an OutOfMemoryError; cannot commit > at > org.apache.lucene.index.IndexWriter.prepareCommitInternal(IndexWriter.java:2668) > at > org.apache.lucene.index.IndexWriter.commitInternal(IndexWriter.java:2834) > at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:2814) > at > org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:529) > at org.apache.solr.update.CommitTracker.run(CommitTracker.java:216) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Apache-Solr-4-after-1st-commit-the-index-does-not-grow-tp4077913p4077924.html > Sent from the Solr - User mailing list archive at Nabble.com.
