Hi, We are building a SolrCloud setup, which will index time-series data. Being time-series data with write-once semantics, we are planning to have multiple collections i.e. one collection per month. As per our use case, end users should be able to query across last 12 months worth of data, which means 12 collections (with one collection per month). To achieve this, we are planning to leverage Solr collection aliasing such that the search_alias collection will point to the 12 collections and indexing will always happen to the latest collection.
As its write-once kind of data, the question I have is whether it is possible to have two different hardware profiles within the SolrCloud cluster such that all the older collections (being read-only) will be stored on the lower hardware spec, while the latest collection (being write heavy) will be stored only on the higher hardware profile machines. - Is it possible to configure a collection such that the collection data is only stored on few nodes in the SolrCloud setup? - If this is possible, at the end of each month, what is the approach to be taken to “move” the latest collection from higher-spec hardware machines to the lower-spec ones? TIA.
