I just tried this. I started 6 nodes with collection1 spread across two shards. Looked at the admin->cloud->graph view and everything looked right and green.
Next, I copy and pasted your command and refreshed the graph cloud view. I see a new collection called consumer1 - all of it's nodes are green and the collection consists of 3 shards. Each shard has 1 leader and 1 replica, each hosted by a different Solr instance. In other words, it seemed to work for me. - Mark On Jan 9, 2013, at 10:58 AM, James Thomas <jtho...@camstar.com> wrote: > Hi, > > Simple question, I hope. > > Using the nightly build of 4.1 from yesterday (Jan 8, 2013), I started 6 Solr > nodes. > I issued the following command to create a collection with 3 shards, and a > replication factor=2. So a total of 6 shards. > curl > 'http://localhost:11000/solr/admin/collections?action=CREATE&name=consumer1&numShards=3&replicationFactor=2' > The end result was the following shard distribution: > shard1 - node #13, #15 (with #13 as leader) > shard2 - node #15, #16 (with #15 as leader) > shard3 - node #11, #16 (with #11 as leader) > > Since I am using the default value of 1 for 'maxShardsPerNode', I was > surprised to see that Solr created two shards on instance #16. I expected > that each Solr node (there are 6) would each be assigned one shard from the > collection. Is this a bug or expected behavior? > > Thanks, > James
