bq: but aren't the config files supposed to be in Zookeeper Yes, but you haven't done anything to tell Solr that the nodes you've created are part of SolrCloud!
You're confusing, I think, core discovery with creating collections. Basically you were pretty much OK up until step 5 (although I'm not at all sure that SOLR_HOST is doing you any good, and certainly setting numShards in SOLR_OPTS isn't a good idea, what happens if you want to create a collection with 5 shards?) You don't need to create any directories on your Solr nodes, that'll be done for you automatically by the collection creation command from the Collections API. So I'd down the nodes and nuke the directories you created by hand and bring the nodes back up. It's probably not necessary to take the nodes down, but I tend to be paranoid about that. Then just create the collection via the Collections API CREATE command, see: https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api1 You can use curl or a browser to issue something like this to any active Solr node, Solr will do the rest: http://some_solr_node:port/solr/admin/collections?action=CREATE&name=mycollection&numShards=2&collection.configName=my_collection_cloud_conf&etc...... I believe it's _possible_ to carefully construct the core.properties files on all the Solr instances, but unless you know _exactly_ what's going on under the covers it'll lead to endless tail-chasing. You can control which nodes the collection ends up on with the createNodeSet parameter etc.... Best, Erick On Mon, Jun 1, 2015 at 4:37 PM, tuxedomoon <dancolem...@yahoo.com> wrote: > I followed these steps and I am unable to launch in cloud mode. > > 1. created / started 3 external Zookeeper hosts: zk1, zk2, zk3 > > 2. installed Solr 5.1 as a service called solrsvc on two hosts: s1, s2 > > 3. uploaded a configset to zk1 (solr home is /volume/solr/data) > ------------------------------------------------------------------- > /opt/solrsvc/server/scripts/cloud-scripts/zkcli.sh -cmd upconfig -zkhost > zk1:2181 -confname mycollection_cloud_conf -solrhome /volume/solr/data > -confdir /home/ec2-user/mycollection/conf > > > 4. on s1, added these params to solr.in.sh > ------------------------------------------------------------------- > ZK_HOST=zk1:2181,zk2:2181,zk3:2181 > SOLR_HOST=s1 > ZK_CLIENT_TIMEOUT="15000" > SOLR_OPTS="$SOLR_OPTS -DnumShards=2" > > > 5. on s1 created core directory and file > -------------------------------------------------------------------- > /volume/solr/data/mycollection/core.properties (name=mycollection) > > > 6. repeated steps 4,5 for s2 minus the numShards param > > > Starting the service on s1 gives me > > mycollection: > org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: > Could not load conf for core mycollection: Error loading solr config from > /volume/solr/data/mycollection/conf/solrconfig.xml > > but aren't the config files supposed to be in Zookeeper? > > Tux > > > > > > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-5-1-startup-looking-for-standalone-config-tp4209118.html > Sent from the Solr - User mailing list archive at Nabble.com.
