Did you look at: http://chronix.io/
Regards, Alex. ---- http://www.solr-start.com/ - Resources for Solr users, new and experienced On 28 March 2017 at 12:33, serwah sabetghadam <sabetgha...@ifs.tuwien.ac.at> wrote: > Dear all, > > Do you know any good reference/best practice for Solr to work with > Time-series data, time-based indexes or retiring data. > As I searched it seems to me that we should simulate the configuration > ourselves through distributed search. > > Any help is highly appreciated, > Best, > Serwah > > > On Fri, Mar 17, 2017 at 3:30 PM, Shawn Heisey <apa...@elyograg.org> wrote: > >> On 3/15/2017 7:55 AM, serwah sabetghadam wrote: >> > Thanks Erick for the fast answer:) >> > >> > I knew about sharding, just as far as I know it will work on different >> > servers. >> > I wonder if it is possible to do sth like sharding as you mentioned but >> on >> > a single standalone Solr? >> > Can I use the implicit routing on standalone then? >> >> If you're running standalone (not SolrCloud), then everything having to >> do with shards must be 100 percent managed by you. There is no >> routing. There is no capability of automatically managing which >> implicit shards belong to which logical index. There's no automatic >> replication of index data for redundancy. You're in charge of >> *everything* that SolrCloud would normally handle automatically. >> >> https://cwiki.apache.org/confluence/display/solr/ >> Distributed+Search+with+Index+Sharding >> >> Multiple shards can live in a single Solr instance, whether you use >> SolrCloud or the old way described above. If your query rate is very >> low, this probably will perform well. As the query rate increases, it's >> best to only have one core per Solr instance. Either way, it's >> *usually* best to only have one Solr instance per machine. >> >> Thanks, >> Shawn >> >> > > > -- > Serwah Sabetghadam > Vienna University of Technology > Office phone: +43 1 58801 188633 <%2B43%201%2058801%20188314>
