At Infoseek, we ran a separate search index with today's updates and merged that in once each day. It requires a little bit of federated search to prefer the new content over the big index, but the daily index can be very nimble for update.
wunder On 8/22/07 7:58 AM, "mike topper" <[EMAIL PROTECTED]> wrote: > Hello, > > Currently in our application we are using the master/slave setup and > have a batch update/commit about every 5 minutes. > > There are a couple queries that we would like to run almost realtime so > I would like to have it so our client sends an update on every new > document and then have solr configured to do an autocommit every 5-10 > seconds. > > reading the Wiki, it seems like this isn't possible because of the > strain of snapshotting and pulling to the slaves at such a high rate. > What I was thinking was for these few queries to just query the master > and the rest can query the slave with the not realtime data, although > I'm assuming this wouldn't work either because since a snapshot is > created on every commit, we would still impact the performance too much? > > anyone have any suggestions? If I set autowarmingCount=0 would I be > able to to pull to the slave faster than every couple of minutes (say, > every 10 seconds)? > > what if I take out the postcommit hook on the master and just have the > snapshooter run on a cron every 5 minutes? > > -Mike > >
