First the numShards parameter is only relevant the very first time you create your collection. It's a little confusing because in the SolrCloud examples you're getting "collection1" by default. Look further down the SolrCloud Wiki page, the section titled "Managing Collections via the Collections API" for creating collections with a different name.
Either way, either when you run the bootstrap command or when you create a new collection, that's the only time numShards counts. It's ignored the rest of the time. As far as data growing, you need to either 1> create enough shards to handle the eventual size things will be, sometimes called "oversharding" or 2> use the splitShard capabilities in very recent Solrs to expand capacity. Best Erick On Thu, Jul 18, 2013 at 4:52 PM, Flavio Pompermaier <pomperma...@okkam.it> wrote: > Hi to all, > Probably this question has a simple answer but I just want to be sure of > the potential drawbacks..when I run SolrCloud I run the main solr instance > with the -numShard option (e.g. 2). > Then as data grows, shards could potentially become a huge number. If I > hadstio to restart all nodes and I re-run the master with the numShard=2, > what will happen? It will be just ignored or Solr will try to reduce > shards...? > > Another question...in SolrCloud, how do I restart all the cloud at once? Is > it possible? > > Best, > Flavio
