Java replication takes slaves down
Hi everybody, we are using Solr 1.4.1 as our search backend and are replicating (Java based) from one master to four slaves. When our index data grew in size (optimized around 4,5 GB) lately we started having huge trouble to spread a new index to the slaves. They run on 100% CPU and are not able to serve request anymore. We have to kill the Java process to start them again... Does anybody have a similar experience? Any hints or ideas on how to set up proper replication? Thanks, Alex
Re: Java replication takes slaves down
We are using a similar architecture but with two slaves, the index is around 9GB * and we don't have such problem... Each slave is running on a separate machine so we have three nodes in total (1 indexer + 2 searcher)...initially it was everything on a single node and it was working without any problem Don't know...try with some tool like jstack in order to see what the JVM is doing... Regards Andrea --Original Message-- From: Alexander Valet | edelight To: solr-user@lucene.apache.org ReplyTo: solr-user@lucene.apache.org Subject: Java replication takes slaves down Sent: Jul 21, 2011 10:39 Hi everybody, we are using Solr 1.4.1 as our search backend and are replicating (Java based) from one master to four slaves. When our index data grew in size (optimized around 4,5 GB) lately we started having huge trouble to spread a new index to the slaves. They run on 100% CPU and are not able to serve request anymore. We have to kill the Java process to start them again... Does anybody have a similar experience? Any hints or ideas on how to set up proper replication? Thanks, Alex
Re: Java replication takes slaves down
How often do you replicate? Could it be a too-frequent-commit problem? (a replication is a commit to the slave). On 7/21/2011 4:39 AM, Alexander Valet | edelight wrote: Hi everybody, we are using Solr 1.4.1 as our search backend and are replicating (Java based) from one master to four slaves. When our index data grew in size (optimized around 4,5 GB) lately we started having huge trouble to spread a new index to the slaves. They run on 100% CPU and are not able to serve request anymore. We have to kill the Java process to start them again... Does anybody have a similar experience? Any hints or ideas on how to set up proper replication? Thanks, Alex
