Actually, I do have an idea what tool to use, bin/solr. But use at
your own risk.
You can use 'bin/solr zk cp -r blah blah blah" to copy the entire
tree down to somewhere local then copy it back up to a different
place. Prior to Solr 6.6, however, this wouldn't work when copying
from root so bewa
On 9/15/2017 10:23 AM, James Keeney wrote:
> However, I'm not sure how to switch the production cluster to explicitly
> reference the directory it currently uses. Do I need to setup the directory
> first?
To set up a *new* cloud under a chroot, you do need to create the chroot
within the ZK databa
Mike -
Thank you, this was very helpful. I've doing some research and
experimenting.
As currently configured solr is launched as a service. I looked at the
sol.in.sh file in /etc/default and we are running using a list of servers
for the zookeeper cluster.
so I think that is translated to -z zoo
When you specify the zk string for a solr instance, you typically include a
chroot in it. I think the default is /solr, but it doesn't have to be, so
you should be able to run with -z zk1:2181/sorl-dev and /solr-prod
https://lucene.apache.org/solr/guide/6_6/setting-up-an-external-zookeeper-ensembl
I have a staging and a production solr cluster. I'd like to have them use
the same zookeeper cluster. It seems like it is possible if I can set a
different directory for the second cluster. I've looked through the
documentation though and I can't quite figure out where to set that up. As
a result m
