At first glance unless I missed something hourglass will definitely not work for our use-case which just involves real time inserts of new log data and no appends at all. However I would like to examine the guts of hourglass to see if we can customize it for our use-case.
> From: arafa...@gmail.com > Date: Mon, 27 May 2013 16:17:12 -0400 > Subject: Re: Keeping a rolling window of indexes around solr > To: solr-user@lucene.apache.org > > But how is Hourglass going to help Solr? Or is it a portable implementation? > > 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 Mon, May 27, 2013 at 3:48 PM, Otis Gospodnetic > <otis.gospodne...@gmail.com> wrote: > > Hi, > > > > SolrCloud now has the same index aliasing as Elasticsearch. I can't lookup > > the link now but Zoie from LinkedIn has Hourglass, which is uses for > > circular buffer sort of index setup if I recall correctly. > > > > Otis > > Solr & ElasticSearch Support > > http://sematext.com/ > > On May 24, 2013 10:26 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
