Hello Solr community folks,
I am doing some investigative work around how to roll and manage indexes inside 
our solr configuration, to date I've come up with an architecture that 
separates a set of masters that are focused on writes and get replicated 
periodically and a set of slave shards strictly docused on reads, additionally 
for each master index the design contains partial purges which get performed on 
each of the slave shards as well as the master to keep the data current.   
However the architecture seems a bit more complex than I'd like with a lot of 
moving pieces.  I was wondering if anyone has ever handled/designed an 
architecture around a "conveyor belt" or rolling window of indexes around n 
days of data and if there are best practices around this.  One thing I was 
thinking about was whether to keep a conveyor belt list of the slave shards and 
rotate them as needed and drop the master periodically and make its backup 
temporarily the master.


Anyways would love to hear thoughts and usecases that are similar from the 
community.

Regards                                           

Reply via email to