FTS-Index SolrCloud Cluster - Standard Deployment Layout

<< Click to show table of contents >>

There are many different ways to set up a load balancing system for Solr.

Describes the recommended layout for WebOffice FTS-Index in most cases.

The following installation instructions also refer to this standard layout.

To guarantee reliability, at least two Solr instances are required. These have to be distributed to different hosts in order to cope with the failure of an entire machine.

Also, several (typically 3) Zookeeper instances must be distributed, typically to different hosts:

Zookeeper is only available if the absolute majority of the defined instances of the ensemble can be reached. Therefore, an odd number of instances is always recommended (at least three), since, for example, with only two instances, the ensemble would no longer be available even if one instance failed. The instances should also be distributed among different hosts.

Typical deployment of WebOffice with SolrCloud

Configuration values of the components involved

Here is an example of a system of three Zookeeper instances and two Solr instances.

The urgent recommendation is to spread the services over several (at least three) hosts.

	Host (recommendation)	Port (recommendation)
Host A
SOLR_PORT	host_A	8983
ZK_CLIENT	host_A	3181
ZK_QUORUM	host_A	2888
ZK_ELECTION	host_A	3888

Host B
SOLR_PORT	host_B	8983
ZK_CLIENT	host_B	3181
ZK_QUORUM	host_B	2888
ZK_ELECTION	host_B	3888

Host C
SOLR_PORT	(not installed)	(not installed)
ZK_CLIENT	host_C	3181
ZK_QUORUM	host_C	2888
ZK_ELECTION	host_C	3888

•Zookeeper should not run on the default port 2181, as this port is typically already used by ArcGIS Server (which uses a stand-alone instance of Zookeeper internally).

•The STOP_PORT for Solr is set implicitly (SOLR_PORT - 1000). However, it must be ensured that this port must also be accessible from outside (e.g. a zookeeper instance) and therefore must not be blocked by the firewall.