Shawn's nailed it. I wanted to add that in 6.4 there are additional commands in bin/solr to explore ZK, e.g. "ls" which also has a recurse option.
Erick On Wed, Feb 22, 2017 at 8:15 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 2/22/2017 8:25 AM, Chris Rogers wrote: >> … as uploaded with upconfig. However, in the /solr directory we have a >> second /configs folder with the old schema.xml within it. I presume >> this is the collection config being used, as it is named simply >> ‘tolkien’ as defined in the create collection command. > > It sounds like Solr is being started with a chroot on the zkHost > string. If tht's true, it means that your upconfig command is using a > different zkHost value, and that's the problem. > > The zkHost string you use should be the same everywhere. Here's an > example of a zkHost specifying a redundant ensemble of three servers, > and confining itself to a "/solr" chroot: > > server1:2181,server2:2181,server3:2181/solr > > The javadoc for CloudSolrClient contains some details on how zkHost > should be constructed: > > http://lucene.apache.org/solr/6_3_0/solr-solrj/org/apache/solr/client/solrj/impl/CloudSolrClient.html#CloudSolrClient-java.lang.String- > > I personally recommend always using a chroot, but if the zookeeper > ensemble is dedicated to a single SolrCloud cluster and no other > software is using it, that wouldn't be necessary. > > Thanks, > Shawn >
