Hi no i see that on a normal request select?q= then I've an xml answer with qtime and clearly when my slave bring back last replication from the master the qtime is very long, so I don't know if it comes from the commit ? or the replication but it affect a lot my respond time answer? Maybe I missed something, I'm unsing replication script solr1.4. I bring back almost 10G every 20mn because I've 2000docs updated every 20mn, so Lucene always merge it.
Can I do something to optimize? Thanks a lot Noble Paul നോബിള് नोब्ळ् wrote: > > where do u see this QTime? > in the stats page? > replication can skew the QTime in master badly because downloading > snapshots is a normal request. > > On Thu, Mar 26, 2009 at 6:59 PM, sunnyfr <johanna...@gmail.com> wrote: >> >> Hi, >> >> Just applied replication by requestHandler. >> And since this the Qtime went mad and can reach long time <int >> name="QTime">9068</int> >> Without this replication Qtime can be around 1sec. >> >> I've 14Mdocs stores for 11G. so not a lot of data stores. >> I've servers with 8G and tomcat use 7G. >> I'm updating every 30mn which is about 50 000docs. >> Have a look as well at my cpu which are aswell quite full ? >> >> Have you an idea? Do I miss a patch ? >> Thanks a lot, >> >> Solr Specification Version: 1.3.0.2009.01.22.13.51.22 >> Solr Implementation Version: 1.4-dev exported - root - 2009-01-22 >> 13:51:22 >> >> http://www.nabble.com/file/p22722028/cpu_.jpg cpu_.jpg >> -- >> View this message in context: >> http://www.nabble.com/replication-%28request-handler%29-Qtime-goes-mad--tp22722028p22722028.html >> Sent from the Solr - Dev mailing list archive at Nabble.com. >> >> > > > > -- > --Noble Paul > > -- View this message in context: http://www.nabble.com/replication-%28request-handler%29-Qtime-goes-mad--tp22722028p22826803.html Sent from the Solr - Dev mailing list archive at Nabble.com.
