Hi Chris, I started a discussion on this topic on the ElasticSearch mailing list the other day. As soon as SolrCloud get index alias functionality (JIRA for it exists) I believe the same approach to cluster expansion will be applicable to SolrCloud as what can be done with ES today:
http://search-lucene.com/m/RZYhi2ydnXD1&subj=Alternatives+to+oversharding+to+handle+index+cluster+growth+ Otis -- Solr & ElasticSearch Support http://sematext.com/ On Thu, Feb 28, 2013 at 7:10 PM, Chris Simpson <chrissimpson1...@outlook.com > wrote: > Dear Lucene / Solr Community- > > I recently posted this question on Stackoverflow, but it doesnt seem to be > going too far. Then I found this mailing list and was hoping perhaps to > have more luck: > > Question- > > If I plan on holding 7TB of data in a Solr Cloud, is it bad practice to > begin with 1 server holding 100 shards and then begin populating the > collection where once the size grew, each shard ultimately will be peeled > off into its own dedicated server (holding ~70GB ea with its own dedicated > resources and replicas)? > > That is, I would start the collection with 100 shards locally, then as > data grew, I could peel off one shard at a time and give it its own server > -- dedicated w/plenty of resources. > > Is this okay to do -- or would I somehow incur a massive bottleneck > internally by putting that many shards in 1 server to start with while data > was low? > > Thank you. > Chris > >
