Unfortunately, for 4.0, the collections API was pretty bare bones. You don't actually get back responses currently - you just pass off the create command to zk for the Overseer to pick up and execute.
So you actually have to check the logs of the Overseer to see what the problem may be. I'm working on making sure we address this for 4.1. If you look at the admin UI, in the zk tree, you should be able to see what node is the overseer (look for its election node). The logs for that node should indicate the problem. FYI, if I remember right, replication factor is not currently optional. In the future, I'd like it so you can say like replicationFactor=max_int, and the overseer will periodically try to match that given the nodes it sees - but we don't have that yet. When you add new nodes, to add them to a current collection you will either have to use CoreAdmin API or pre configure the cores in solr.xml. All you need is to specify a matching collection name for the new core. - Mark On Jan 2, 2013, at 7:58 PM, davers <dboych...@improvementdirect.com> wrote: > Hello I have an external zookeeper ensemble and I have started 6 tomcat > servers with solr running with the default solr.xml > > I have uploaded the config directory to zookeeper and linked the collection. > > http://d.pr/i/BkT > > My solr.xml is nearly the default with a minor adjustment for the jetty.port > parameter: > > <cores adminPath="/admin/cores" defaultCoreName="collection1" > host="${host:}" hostPort="${jetty.port:8080}" hostContext="${hostContext:}" > zkClientTimeout="${zkClientTimeout:15000}"> > </cores> > > When I try to create the collection issuing the command: > /solr/admin/collections?action=CREATE&name=productindex&numShards=3 (I leave > replicationFactor out because I want my cloud to automatically re-size > vertically as I add or remove replicant servers) I get output in the log: > > INFO: Creating Collection : numShards=3&name=productindex&action=CREATE > > But nothing happens. The solr.xml files are not updated. What am I doing > wrong? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Collection-API-doesn-t-seem-to-be-working-tp4030182.html > Sent from the Solr - User mailing list archive at Nabble.com.