Re: almost realtime updates with replication

n snappuller on your slave machines ever 5 minutes (the >>>> snapshots are hardlinks and don't take up a lot of space, and snappuller >>>> only needs to fetch the most recent snapshot) >>>> >>>> your idea of querying the msater directly for these queries se

Re: almost realtime updates with replication

up a lot of space, and snappuller >>> only needs to fetch the most recent snapshot) >>> >>> your idea of querying the msater directly for these queries seems >>> perfectly fine to me ... just make sure the auto warm count on the >>> caches >>> on your master is very

Re: almost realtime updates with replication

y fine to me ... just make sure the auto warm count on the caches >> on your master is very tiny so the new searchers are ready quickly after >> each commit. >> >> >> >> >> -Hoss >> >> >> > > -- > View this message in context: > http://www.nabble.com/almost-realtime-updates-with-replication-tp12276614p22034406.html > Sent from the Solr - User mailing list archive at Nabble.com. > > -- --Noble Paul

Re: almost realtime updates with replication

rying the msater directly for these queries seems > perfectly fine to me ... just make sure the auto warm count on the caches > on your master is very tiny so the new searchers are ready quickly after > each commit. > > > > > -Hoss > > > -- View this messag

Re: almost realtime updates with replication

: : 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

Re: almost realtime updates with replication

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 PROTECT

almost realtime updates with replication

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