I'm pretty confused about what you're trying to do. You mention using the SolrCloud UI to look at your core, but on the other hand you also mention using the core admin to create the core.
Trying to use the core admin commands with SolrCloud is a recipe for disaster. Under the covers, the _collections_ api does, indeed, use the core admin API to create cores, but it really must be precisely done. If you're going to try to create your own cores, I recommend setting up a non-SolrCloud system. If you want to use SolrCloud, then I _strongly_ recommend you use the collections API to create your collections. You can certainly have a single-shard collection that would be a leader-only collection (i.e. no followers), which would have only a single core cluster-wide if that fits your architecture.... As it is, in cloud mode Solr expects the configs to be up on Zookeeper, not resident on disk somewhere. And the admin core create command promises that you have the configs in /Users/nw/Downloads/twc-session-dash/collection1 which is a recipe for confusion on Solr's part... HTH, Erick On Thu, Oct 29, 2015 at 4:24 PM, natasha <nata...@factual.com> wrote: > Note, if I attempt to CREATE the core using Solr 5.3.0 on my openstack > machine (Java version 1.7.0) I have no issues. > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-5-3-1-CREATE-defaults-to-schema-less-mode-Java-version-1-7-0-45-tp4237305p4237307.html > Sent from the Solr - User mailing list archive at Nabble.com.