Hi, We recently had production release to upgrade our Solr3.5 to Solr 4.2.1. (No schema change except the some basic required for 4.2.1)
The nature of our document is that we have huge multivalued fields. they can go from 1000 to 100K in once single field. # Documents : 300K # Index size: 9GB (all fields are stored and 5 are index) # JVM Heap: 4GB We haven't seen more than 10% CPU and 60% JVM heap during our usage where we get 7K to 10K request per min for this server. Upgrading to 4.2.1 we saw the CPU spiked to constant 75% and heap usage grew to 95% within 5 mins of traffic. Later the server becomes slow to unresponsive and we start seeing connection timeouts Did couple of adjustments to JVM heap but still couldn't get it resolved. and had to rollback to 3.5 as we were exceeding out deployment window. During our investigation we identified that the queries which are causing the problem is the one which is fetching the huge multivalued fields. Decompressing is killing the server. I have reported this issue earlier which happened to be fixed in 4.2.1 but not sure if there is another side effect of compressed field that still remains. Any advice is much appreciated. thanks Aditya -- View this message in context: http://lucene.472066.n3.nabble.com/Rollback-from-Solr4-2-1-to-Solr3-5-tp4067094.html Sent from the Solr - User mailing list archive at Nabble.com.
