On 10/9/2016 1:59 PM, Reinhard Budenstecher wrote: > Solr 6.2.1 on Debian Jessie, installed with: <snip> > Actually, there are three cores and UI gives me following info: > Num Docs:148652589, Max Doc:298367634, Size:219.92 GB Num > Docs:37396140, Max Doc:38926989, Size:28.81 GB Num Docs:8601222Max > Doc:9111004, Size:6.26 GB
That's considerably larger than you initially indicated. In just one index, you've got almost 300 million docs taking up well over 200GB. About half of them have been deleted, but they are still there. Those deleted docs *DO* affect operation and memory usage. Getting rid of deleted docs would go a long way towards reducing memory usage. The only effective way to get rid of them is to optimize the index ... but I will warn you that with an index of that size, the time required for an optimize can reach into multiple hours, and will temporarily require considerable additional disk space. The fact that your index is on SSD will probably not improve the performance of an optimize. When I have looked into optimize performance, it typically proceeds at a much slower pace than most disks can sustain, because Lucene must process the data as it rewrites it. > Actually, Solr servers dies nearly once a day, on next shutdown, I'll > reduce the heap size. I don't know if that's going to help, but it might. > How do I create such a stack trace? I have no more log informations > than the already posted ones. You don't need to create it. Stacktraces are logged by Solr, in a file named solr.log, whenever most errors occur. Thanks, Shawn
