This is kind of the approach used by elastic search , if I'm not using solrcloud will I be able to use shard aliasing, also with this approach how would replication work, is it even needed?
Sent from my iPhone On May 24, 2013, at 12:00 PM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > Would collection aliasing help here? From Solr 4.2 release notes: > Collection Aliasing. Got time based data? Want to re-index in a > temporary collection and then swap it into production? Done. Stay > tuned for Shard Aliasing. > > Regards, > Alex. > Personal blog: http://blog.outerthoughts.com/ > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > - Time is the quality of nature that keeps events from happening all > at once. Lately, it doesn't seem to be working. (Anonymous - via GTD > book) > > > On Fri, May 24, 2013 at 10:25 AM, Saikat Kanjilal <sxk1...@hotmail.com> wrote: >> 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 >
