You have no cache at all when you stop and restart Solr. I recommend using the provided scripts for index distribution. Run snappuller and snapinstaller every two hours.
The scripts already do the right thing. A snapshot is created after a commit on the indexer. Snappuller only copies over an index when it has changed. Snapinstaller updates Solr without restarting it. Solr autowarms a new cache from the existing one. wunder On 2/28/08 7:12 PM, "Alex Benjamen" <[EMAIL PROTECTED]> wrote: > I'm trying to figure out how best to handle the replication for our system. > (We're > not using the rsync mechanism because we don't want to have frequent updates > on slaves) > > Current process: > > 1. Master builds new incremental index once an hour. Commit/Optimize, copy > over > index to an nfs exported directory > 2. Slave compares index version on in mounted dir to it's own(once in 2hrs), > if it finds a newer > index, it will: stop solr, copy over new index, restart solr > > Things are working fine, but, the problem is there is no autowarming. If we > use the master/slave > setup, then rsync will constantly update the index and the caching will not > work as well. There > is no reason for us to keep updating the slaves. > > Question: is it possible to simply copy over the new index without restarting > solr? And solr server > will detect that the index has in fact changed, and autowarm based on prev. > queries... > > Should snappuller be used? How does snappuller know not to fetch while the > master is indexing > the feeds... or doing optimize, etc > > Thanks in advance for sugesstions > -Alex
