Sujatha, A few thoughts: * If you are still using rsync replication, you may be using an old version of Solr. Consider upgrading (it's also more efficient with memory). * Yes, rsync will "pollute" OS cache, but is it really pollution if it makes the OS cache the index that is about to be made searchable? * You typically want to replica only changed portions of the index, not whole indices, so maybe there is no need to worry about this. * If you've properly warmed up the index after replication and searches are still taking a long time, then it's likely that query latency is unrelated to replication and "pollution". * Monitor your disk IO, CPU usage, and Solr cache usage - this will likely lead you in the right direction.
Otis ---- Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm >________________________________ > From: Sujatha Arun <suja.a...@gmail.com> >To: solr-user@lucene.apache.org >Sent: Sunday, June 3, 2012 4:32 AM >Subject: OS memory Pollution on rsync? > >Hello, > >When we migrated the solr webapps to a new server in production,We did an >rsync of all the indexes in our old server . On checking with Jconsole >,the OS free Ram was already filled to twice the Index size .There is no >other service in this server. The rsync was done twice. > >Even though we have more RAM in the new server ,some of the simple queries >are taking more than 2s to execute .If index was cached ,then why its >taking so long to execute > > >Any ideas? > >Regards >Sujatha >* >* > > >
