Hi Shawn,
Thanks. I am indeed using a chroot.
In my solr.in.ih file I have the following:
ZK_HOST="172.28.128.9/solr"
I think I understand you’re saying that I need to specify this chroot dir in
the upconfig command? Where should this be specified? Something like:
bin/solr zk upconfig -z 172.28.128.9:2181 -n solr/configs/tolkien -d
/home/bodl-tei-svc/solr-6.4.0/server/solr/configsets/tolkien_config
Thank you for your help with this.
Best,
Chris
On 22/02/2017, 16:15, "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
