Hello, Erik. Thank you for answering again. I'm using Java JDK 1.5 and an Apache Tomcat 1.6 configuring it's memory parameters from 1G to 2G maximum for each Tomcat server. The machine has a RAID5 HDD, 32G RAM and eight cores, and I have six Tomcat launched with their process running at the same time. However, I think that the computer is enough powerful to handle the workload. Well, at least I thought that... Finally, I'm optimizing the index one time per two nights, but no indexing is in process, because I've got an Active MQ queue that queues petitions while optimization is in progresss and then index them. The alternatives that I think that could solve the problem are:
1. Updating Solr version and check the behaviour. I think that the latest versions have replication improvements. 2. Control (right now I don't know how) the replication and index operations so that I'll activate replication in slaves queueing new petitions (the no index will be in progress) and then re-activate it after replication. It's a bit complicated, but posible. Any alternative would be welcome, :-) Thank you for your help.
