Out of curiosity, did you figure out the cause or did the OOMs just go away with a nightly build?
Otis -- Solr & ElasticSearch Support http://sematext.com/ On Sat, Dec 29, 2012 at 8:08 PM, shreejay <shreej...@gmail.com> wrote: > Otis, > > As of now I have disabled caches. And we are hardly running any queries at > this point. I filter mostly on string fields and two int fields, 2 dates > (one is a dynamic date field) and one dynamic string field. Same goes for > faceting also, except I do not use facets on the dynamic field. > > In terms of documents , my index is around 5.5 million. > > I am not trying to rule out the possibility of queries causing this, but I > think its highly unlikely. The cluster is being used only by a select few > and I have noticed this behaviour generally during indexing (which happens > mostly during the night). > > The Autocommit with 0 values seems to be working. I am constantly > monitoring > the logs and I can see commits happening only every 30 and 60 min > intervals. > These commits are run by a cron job. > > Shawn, > > Your assumption is right! Thanks for the tips on Solconfig changes. They > have been working good most of the times. I am assuming these issues come > up > after a couple of million of documents are indexed. During the initial > indexing (upto 3-4 million docs) everything seems to be fine. I am going to > try the recent nightly build apache-solr-4.1-2012-12-28_12-29-23 now. Lets > hope using 4.1 fixes these issues. I have already started indexing my > documents on a 3.6.2 Solr box as a backup. I am also going to reduce the > JVM > heap size and experiment between 8 - 10 GB, since i think some of the ZK > connection issues were happening due to longer GC pauses. > > > Thanks Jack for verifying it in the code. > > --Shreejay > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Frequent-OOM-Unknown-source-in-logs-tp4029361p4029657.html > Sent from the Solr - User mailing list archive at Nabble.com. >
