Otis Gospodnetic wrote:
Geoff,
There was just another thread where the person said he was doing
updates every 2 minutes.
ok, I see that now. unfortunately, the data is sparse there :)
Like you said, with the way Solr warms
searchers, this could be too frequent for instances with large caches
and high autowarmCount.
ok, thanks.
I'll have a better sense of the size of my data soon, but I suspect it's
nowhere near on the scale of most of the people here - maybe a million
documents, tops. right now I'm proof-of-concept'ing nearly all our data
(but in a single language) and it's 500K documents with an index of 100M :)
You may be better off playing with the combination of larger older
index and a smaller index with updates kept in RAM (on the slave, of
course).
good info, thanks.
sorry for the basic questions. and thanks for the (later) pointer to
solr-303 - I found the distributed search docs from there and will keep
that in mind as I move forward.
--Geoff
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ---- From: Geoffrey Young
<[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent:
Thursday, April 17, 2008 8:28:09 AM Subject: config for very frequent
solr updates
hi all :)
I didn't see any documentation on this, so I was wondering what the
experience here was with updating solr with a small but constant
trickle of daemon-style updates.
unfortunately, it's a business requirement that backend db updates
make it to search as the changes roll in (5 minutes is out of the
question). with the way solr handles new searchers, warming, etc, I
was wondering if anyone had experience with this kind of thing and
could share thoughts/general config stuff on it.
thanks.
--Geoff
