: I've reviewed the wiki pages about snappuller : (http://wiki.apache.org/solr/SolrCollectionDistributionScripts) and : solrconfig.xml (http://wiki.apache.org/solr/SolrConfigXml) and it : seems that the snappuller is intended to be used on the slave server. : In our case, the slave servers do no updating and never commit; the : master is the only one that commits. Is there a standard way for the : just-committed, consistent index to be pushed from the master server : out to the slaves?
the master runs snapshooter in either a postCommit or postOptimize hook. the slaves run snappuller and snapinstaller via schedule (or manually) ...maybe that's what you are already doing ... but earlier in this thread when yonik asked about postCommit you said... > > Are you using the postCommit hook in solrconfig.xml to call snapshooter? > > No, just the crontab. We have only one master server on which commits > are made, and the servers on which requests are made run the > snapshooter periodically. No data changes are made on the read > servers, so postCommit would never be called anyway (I believe). ...which (as i read it, and i'm pretty sure yonik read it the same way) means you are running snapshooter on your slave machiens (ie: "servers on which requests are made") ... there is (normally) no reason to run snapshooter on those machines ... which (along with the other stuff you're written) makes it seem like maybe you are getting the index off the master in some unrecommended way (and getting it before the delets which have been batched up are processed) and then only using the scripts on the slave/query machines. Then again: this may all be a Red Herring and totally unrelated to your problem. -Hoss
