Are you defining shard and replicas here? Or is this just a single-node collection? In any case, this seems unnecessary. You'd get the same thing by having your uploading the config set to ZK, then just issuing a Collections CREATE command, specifying the node to use if desired.
What you're doing _should_ work, because essentially that's what start up does. It finds cores somewhere below SOLR_HOME and reads the core.properties file. When it finds parameters like collection, shard, coreNodeName, numShards, all that stuff it figures things out. But, you have to get all this right manually with the process you're using now, why take the risk? Besides, in the future you'll have to adapt to any back-compat breaks... Best, Erick On Wed, May 27, 2015 at 8:34 AM, Jim.Musil <jim.mu...@target.com> wrote: > bump > > On 5/21/15, 9:06 AM, "Jim.Musil" <jim.mu...@target.com> wrote: > >>Hi, >> >>In the guide for moving from Solr 4.x to 5.x, it states the following: >> >>"Solr 5.0 only supports creating and removing SolrCloud collections >>through the Collections >>API<https://cwiki.apache.org/confluence/display/solr/Collections+API>, >>unlike previous versions. While not using the collections API may still >>work in 5.0, it is unsupported, not recommended, and the behavior will >>change in a 5.x release." >> >>Currently, we launch several solr nodes with identical cores defined >>using the new Core Discovery process. These nodes are also connected to a >>zookeeper ensemble. Part of the core definition is to set the configSet >>to use. This configSet is uploaded to zookeeper separately. This >>effectively creates a Collection. >> >>Is this method no long supported in 5.x? >> >>Thanks! >>Jim Musil >> >
