Are you using all those cores at once? If not, there is a recent settings to allow solr to load cores on demand.
If you are using them all, perhaps you need to look into splitting them to different machines (horizontal scaling). What about your caches? How many additional structures you have configured for each core? How much memory you allocated to the Java process. You are probably running out of memory and thrashing with a swap. I am not even sure Java process can access that much memory in one process. You might be better off running multiple Tomcat/Solr instances on the same machine with different subsets of cores. Regards, Alex. P.s. This is general advice, I don't know the specific issues around that version of Solr/Tomcat. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Thu, Apr 10, 2014 at 1:40 PM, Atanas Atanasov <atanaso...@gmail.com> wrote: > Hi, guys, > > I need some help. After updating to SOLR 4.4 the tomcat process is > consuming about 2GBs of memory, the CPU usage is about 40% after the start > for about 10 minutes. However, the bigger problem is, I have about 1000 > cores and seems that for each core a thread is created. The process has > more than 1000 threads and everything is extremely slow. Creating or > unloading a core even without documents takes about 20 minutes. Searching > is more or less good, but storing also takes a lot. > Is there some configuration I missed or that I did wrong? There aren't many > calls, I use 64 bit tomcat 7, SOLR 4.4, latest 64 bit Java. The machine has > 24 GBs of RAM, a CPU with 16 cores and is running Windows Server 2008 R2. > Index is uppdated every 30 seconds/10 000 documents. > I haven't checked the number of threads before the update, because I didn't > have to, it was working just fine. Any suggestion will be highly > appreciated, thank you in advance. > > Regards, > Atanas
