Hi Guys,

We have a problem in our current installation after a migration from Apache 
Solr 1.4 to 3.2.
Every time an optimize runs with any other part interfering with the index 
(DIH, replication etc.), then the optimize doesn't finish and slowly starts to 
use up all RAM on the server.

It can however do an optimize if none of the other applications are running, so 
I am thinking sync. problems.

Have anybody else seen this in their migrations?

Best regards,

Dennis Peitersen

Reply via email to