by a commit is not seen
by users until it has been warmed, at which point it is atomically swapped.
-Kallin Nagelberg
-Original Message-
From: Chris Hostetter [mailto:hossman_luc...@fucit.org]
Sent: Wednesday, May 19, 2010 2:38 PM
To: solr-user@lucene.apache.org
Subject: Re: disable c
: I've always undestand that if you do a commit (replication does it), a new
: searcher is open, and you lose performance (queries per second) while the
: caches are regenerated. I think i don't explain correctly my situation
not if you configure your caches with autowarming -- then solr will war
Hi Chris,
Thank you for your answer.
I've always undestand that if you do a commit (replication does it), a new
searcher is open, and you lose performance (queries per second) while the
caches are regenerated. I think i don't explain correctly my situation
before, with my schema i want to avoid t
: I want to know if there is any approach to disable caches in a specific core
: from a multicore server.
only via hte config.
: I have a multicore server where the core0 will be listen to the queries and
: other core (core1) that will be replicated from a master server. Once the
: replication ha
Any suggestions?
I have thought in have two configurations per server and reload each one
with the appropiated config file but i would prefer another solution if its
possible.
Thanks,
Marco Martínez Bautista
http://www.paradigmatecnologico.com
Avenida de Europa, 26. Ática 5. 3ª Planta
28224 Pozu
