Re: disable caches in real time

2010-05-19 Thread Marco Martinez
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 this loss of performance in an
enviroment with frequent updates.

Marco Martínez Bautista
http://www.paradigmatecnologico.com
Avenida de Europa, 26. Ática 5. 3ª Planta
28224 Pozuelo de Alarcón
Tel.: 91 352 59 42


2010/5/18 Chris Hostetter hossman_luc...@fucit.org

 : 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 has been done, i will swap the cores. My point is that i want
 to
 : disable the caches in the core that is in charge of the replication to
 save
 : memory in the machine.

 that seems bizarely complicated -- replication can work against a live
 core, no need to do the swap yourself, the replicationHandler takes care
 of this for your transparently (ie: you have one core, replicating from a
 master -- the old index will be searched by users, and have caches, and
 when the new version of the index is ready, the replication handler will
 swap the *index* in that core (but the core itself never changes) ... it
 can even autowarm the caches on the new index for you before the swap if
 you configure it that way.

 -Hoss




Re: disable caches in real time

2010-05-19 Thread Chris Hostetter

: 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 warm 
up the new caches (on the new index) while the old index still serves 
requests -- this is all manged for you by the SolrCore, no need for core 
swapping.


-Hoss



RE: disable caches in real time

2010-05-19 Thread Nagelberg, Kallin
I suppose you are still losing some performance on the replicated box since it 
needs to use some resources to warm the cache. It would be nice if a warmed 
cache could be replicated from the master though perhaps that's not practical. 
Chris is right though: The newly updated index created 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 caches in real time


: 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 warm 
up the new caches (on the new index) while the old index still serves 
requests -- this is all manged for you by the SolrCore, no need for core 
swapping.


-Hoss



Re: disable caches in real time

2010-05-18 Thread Chris Hostetter
: 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 has been done, i will swap the cores. My point is that i want to
: disable the caches in the core that is in charge of the replication to save
: memory in the machine.

that seems bizarely complicated -- replication can work against a live 
core, no need to do the swap yourself, the replicationHandler takes care 
of this for your transparently (ie: you have one core, replicating from a 
master -- the old index will be searched by users, and have caches, and 
when the new version of the index is ready, the replication handler will 
swap the *index* in that core (but the core itself never changes) ... it 
can even autowarm the caches on the new index for you before the swap if 
you configure it that way.

-Hoss



Re: disable caches in real time

2010-05-17 Thread Marco Martinez
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 Pozuelo de Alarcón
Tel.: 91 352 59 42


2010/5/14 Marco Martinez mmarti...@paradigmatecnologico.com

 Hi,

 I want to know if there is any approach to disable caches in a specific
 core from a multicore server.

 My situation is the next:

 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 has been done, i will swap the cores. My point is that i want to
 disable the caches in the core that is in charge of the replication to save
 memory in the machine.

 Any suggestions will be appreciated.

 Thanks in advance,


 Marco Martínez Bautista
 http://www.paradigmatecnologico.com
 Avenida de Europa, 26. Ática 5. 3ª Planta
 28224 Pozuelo de Alarcón
 Tel.: 91 352 59 42