Hi, The CollectionAPI provides some more options that will prove to be very usefull to you: /admin/collections?action=CREATE&name=name&numShards=number&replicationFactor=number&maxShardsPerNode=number&createNodeSet=nodelist&collection.configName=configname
Have a look at: https://cwiki.apache.org/confluence/display/solr/Collections+API Regarding your observations: 1. Completely normal, that's standard naming 2. When you created the collection you did not specify a configuration so the new collection will use the conf already stored in ZK. If you have more than one not sure which one will be picked as default. 3. You should be able to create replicas, by adding new cores on the other machines, and specifying the collection name and shard id. The data will then be replicated automatically to the new node. If you already tried that and get errors/problems while doing it provide some more details. As far as i know you should be able to move/replace the index data, as long as the source collection has the same config as the target collection. Afterwards you'll have to reload your core / restart the Solr instance - not sure which one will do it - most likely the latter. But it will be easier if you use the method described at point 3 above. Please someone correct me, if i'm wrong. ----- Thanks, Michael -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-question-tp4101266p4101675.html Sent from the Solr - User mailing list archive at Nabble.com.
