Hi, On Tuesday, July 15, 2014 1:20:39 AM UTC-4, Patrick Proniewski wrote: > > Hello, > > Curator makes is possible to migrate an index to another storage > programmatically, and that's very nice to keep old indices on cheap > storage. But if I understand correctly, a unique ES cluster cannot handle > two different storages. Hence, having small but fast storage for recent > files and cheap but slow storage for old files requires building two > clusters. > Am I right? >
Not necessarily. We used the tiered storage approach in Logsene <http://sematext.com/logsene/>, for example, but we explicitly move older indexes to from more expensive nodes that deal with fresh data to cheaper nodes that host all data. It's automated, but it's not 100% done within ES. But it's done with a single ES cluster. Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0bbe88ad-4c60-4383-8ae9-13ab15d02676%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
