: and I though a true master-slave setup would be overkill. Is it really
: problematic to run queries on instances that aren't auto-warmed? Sounds like

it really depends on your usecases and what you consider "problematic" ... 
there's no inherent problem in having queries hit an unwarmed index, it 
isn't an error case or anything like that ...it's just that that those 
queries *may* be slower then you're willing to live with, and if 
you hit an unwarmed index with a high volume of concurrent requests they 
*may* all be slow and they *may* cause general performance problems that 
could cascade ... 

the only hard and fast rule is that regardless of wether it's a master or 
a slave, you don't want to have "commits" (either explicitly on a master 
or because of new snapshots on a slave) happen faster then you can open a 
new searcher -- if they are, then you either need to do less warming when 
opening a newSearcher, or slow down on the commits.

: I'm stuck between a rock and a hard-place. Am I going to have to build my
: initial index w/ one configuration and then re-start with a different
: configuration? I'd prefer to avoid that.

this is where a master/slave setup typically comes into play ... build 
your initial index on a master with replication disabled, wait for a full 
build then enable replication and let your slave(s) pull the full index, 
warm it and then use it.

in theory, you could have "cascading" replication ... where real time 
update go to M which has rapid autocommiting turned on and generates 
snapshots on every commit -- but cache autowarming is completley disabled.  
S1 pulls from M as fast as it can and has some caches with extremely 
conservative cache warming; it responds to queries that need very "up to 
date" info but are willing to wait a little bit i nthe event of a cache 
miss.  S2 pulls from M (or S1) much less frequently then S1 pulls from M, 
S2 has very aggressive cache warming and is used for responding to the 
bulk of queries, where responses need to be generated instantly but the 
info in those responses is allowed to be a little stale.


-Hoss

Reply via email to