On 5/17/2013 1:17 AM, J Mohamed Zahoor wrote: > I moved to 4.2.1 from 4.1 recently.. everything was working fine until i > added few more stats query.. > Now i am getting this error frequently that solr does not run even for 2 > minutes continuously. > All 5GB is getting used instantaneously in few queries...
Someone on IRC ran into memory problems upgrading from 4.0 to 4.2. It wasn't OOM errors, they were just using a lot more heap than they were before and running into constant full garbage collections. There is another message on this list about someone who upgraded from 3.5 to 4.2 and is having memory troubles. The person on IRC made most of their fields unstored and reindexed, which fixed the problem for them. They only needed a few fields stored. Because the IRC user was on 4.0, I originally thought it had something to do with compressed stored fields, but on this thread, they started with 4.1. If that was the released 4.1.0 and not a SNAPSHOT version, then they had compressed stored fields before the upgrade. The user on IRC was not using termvectors or docvalues, which would be potential pain points unique to 4.2. I'm using 4.2.1 with no trouble in my setup, but I do have a heap that's considerably larger than I need. There are no apparent memory leaks - it's been running for over a month with updates once a minute. I've finally switched over from the 3.5.0 index to the new one, so for the last few days, it has been also taking our full query load. What could have changed between 4.1 and 4.2 to cause dramatically increased memory usage? >From my /admin/system: <date name="startTime">2013-04-05T15:52:55.751Z</date> Thanks, Shawn
