lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-3488) Create a Collections API for SolrCloud
Date Fri, 14 Sep 2012 09:29:08 GMT


Jan Høydahl commented on SOLR-3488:

I've been playing with the collections API lately.

First, I am more in favor of the approach where all config and config changes are done against
ZK. I do not like the idea of having to start a solr node in order to define a new collection
or change various configs. All initial config as well as config changes should be possible
to check in to source control and roll out to a cluster as files without starting and stopping
live nodes (perhaps except ZK itself).

Then regarding the current collections API. I don't know if it is by design or a bug:
* Start a master, boostrapping collection1 from local config
* Create another collection specifying number of replicas using the collection API: http://localhost:8983/solr/admin/collections?action=CREATE&name=demo&numShards=1&numReplicas=5
* Add more Solr nodes to the cluster
* The original collection "collection1" starts using the extra nodes as replicas, but the
new "demo" collection does not
> Create a Collections API for SolrCloud
> --------------------------------------
>                 Key: SOLR-3488
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>         Attachments: SOLR-3488_2.patch, SOLR-3488.patch, SOLR-3488.patch, SOLR-3488.patch

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message