Which method do you use to index? If you are using SolrJ you can use the streaming update server it is a better option for the solr server, because the server does not need to held it all in memory.
(if you are using the post.jar file there was bug which causes OOMs but I didn't remember exactly ...) then, when the solr server crashed, it cannot remove the lock file. if you are sure there is only one indexing process you could specify remove <indexDefaults> <lockType>native</lockType> <!-- or any other possible too ?? --> <unlockOnStartup>true</unlockOnStartup> </indexDefaults> see also: -> http://www.mail-archive.com/solr-user@lucene.apache.org/msg08049.html -> "Out Of Memory Errors" on http://wiki.apache.org/solr/SolrPerformanceFactors Regards, Peter. > I am getting it while indexing data to solr not while querying... > Though I have enough memory space upto 40GB and I my indexing data is just > 5-6 GB yet that particular error is seldom observed... (SEVERE ERROR : JAVA > HEAP SPACE , OUT OF MEMORY ERROR ) > I could see one lock file generated in the data/index path just after this > error. > > > > On Tue, Aug 17, 2010 at 4:49 PM, Peter Karich <peat...@yahoo.de> wrote: > > >> >>> Is there a way to verify that I have added correctlly? >>> >>> >> on linux you can do >> ps -elf | grep Boot >> and see if the java command has the parameters added. >> >> @all: why and when do you get those OOMs? while querying? which queries >> in detail? >> >> Regards, >> Peter. >>
