Configuring TORO Integrate to Work with SolrCloud
The ability to connect TORO Integrate to a SolrCloud cluster is already a built-in feature and is just a matter of a few simple configuration changes. However, before doing this, you should make sure that connecting to SolrCloud is supported by your TORO Integrate license.
Navigate to TORO Integrate's
Open your instance properties file and edit the
This property value should be
cloud; this is to tell TORO Integrate we'll be using SolrCloud. It triggers TORO Integrate to use the delegating version of Solr. That is, TORO Integrate will iterate through a list of declared Solr servers and use the first server that successfully connects to a Solr core.
Delegating Solr servers
TORO Integrate also ships with a built-in feature that allows it to use an embedded Solr server in place of the cloud or remote Solr cluster when the latter is unavailable.
This feature is turned off, by default, but you can turn it on by setting the
solr.embedded.delegate.serverinstance property value to
The comma-separated IP addresses of the ZooKeeper instances in your ZooKeeper ensemble.
The prefix of your collection names.
Here's how we did ours:
1 2 3
solr.mode=cloud solr.url=192.168.21.71:2181,192.168.21.72:2181,192.168.21.73:2181 solr.prefix=jte
Restart your TORO Integrate instance. This time, it should connect to your SolrCloud cluster.
cd <toro-integrate-home>/bin/ ./toro-integrate start
While TORO Integrate is starting, check the logs to see if the collections have been initialized properly. You should see something similar to the logs below if TORO Integrate was able to communicate properly with the SolrCloud cluster:
1 2 3 4
25/04/18 08:56:49.402 INFO [CloudSolrServer] Starting core: core/tracker 25/04/18 08:56:49.963 INFO [CloudSolrServer] Starting core: core/tracker completed 25/04/18 08:56:49.977 INFO [CloudSolrServer] Starting core: core/invoke_monitor 25/04/18 08:56:50.037 INFO [CloudSolrServer] Starting core: core/invoke_monitor completed
That's it! Your TORO Integrate instance is now using the SolrCloud cluster that you have just configured!