Even with your current setup (if it's done correctly) slavs should not be returning 0 hits for a query that previously returned hits. That is, nothing should be off-line. Index searcher warmup and swapping happens in the background and while that's happening the old searcher should be serving queries.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Jacob Singh <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Saturday, September 20, 2008 5:54:39 AM > Subject: How to keep a slave offline until the index is puller from master > > Hi, > > I'm running multiple instances (solr 1.2) on a single jetty server using JNDI. > > When I launch a slave, it has to retrieve all of the indexes from the > master server using the snapuller / snapinstaller. > > This works fine, however, I don't want to wait to activate the slave > (turn on jetty) while waiting for every slave to get its data. > > Is there anyway to make sure that a slave is "up2date" before letting > it accept queries? AS it is, the last slave will take 10-15 to get > its data, and for those 15 minutes, it is active in the load balancer > and therefor taking requests which return 0 results. > > Also, if I switch to multi-core (1.3) is this problem avoided? > > Thanks, > Jacob > > > > > -- > > +1 510 277-0891 (o) > +91 9999 33 7458 (m) > > web: http://pajamadesign.com > > Skype: pajamadesign > Yahoo: jacobsingh > AIM: jacobsingh > gTalk: [EMAIL PROTECTED]
