You need to give us more of the exception trace, the real cause is often buried down the stack with some text like "Caused by..."
But at a glance your cache sizes and autowarm counts are far higher than they should be. Try reducing particularly the autowarm count down to, say, 16 or so. It's actually rare that you really need very many. I'd actually go back to the defaults to start with to test whether this is the problem. Further, we need to know exactly what you mean by "change anything in the configuration file". Change what? Details matter. Of course the last thing you changed before you started seeing this problem is the most likely culprit. Best, Erick On Wed, Dec 4, 2013 at 8:31 AM, kumar <pavan2...@gmail.com> wrote: > I am having almost 5 to 6 crores of indexed documents in solr. And when i > am > going to change anything in the configuration file solr server is going > down. > > As a new user to solr i can't able to find the exact reason for going > server > down. > > I am using cache's in the following way : > > <filterCache class="solr.FastLRUCache" > size="16384" > initialSize="4096" > autowarmCount="4096"/> > <queryResultCache class="solr.FastLRUCache" > size="16384" > initialSize="4096" > autowarmCount="1024"/> > > and i am not using any documentCache, fieldValueCahe's > > Whether this can lead any performance issue means going server down. > > And i am seeing logging in the server it is showing exception in the > following way > > > Servlet.service() for servlet [default] in context with path [/solr] threw > exception [java.lang.IllegalStateException: Cannot call sendError() after > the response has been committed] with root cause > > > > Can anybody help me how can i solve this problem. > > Kumar. > > > > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Performance-Issue-tp4104907.html > Sent from the Solr - User mailing list archive at Nabble.com. >
