Follow the steps in Section 1.1, Changing Configuration Options for the Filr Appliance.
You can modify the following configuration options:
Enable Clustered Environment: Select this option to enable clustering.
JVM Route: If you plan to use Apache as the reverse proxy, add a JVM route for each filr Appliance in the Cluster. Otherwise, you can leave the JVM Route field empty. The purpose of this field is to uniquely identify each Filr Appliance to Apache.
In the JVM Route field, specify worker1. On the second Filr node, in the JVM Route field, specify worker2, and so forth for each Filr node, incrementing the JVM Route setting. Each Tomcat instance should have a unique JVM Route setting.
worker1, worker2, and so forth are the default names for the matching values used for the reverse proxy configuration. For example, if you have set up Apache or IIS as a reverse proxy, these are the default values. The JVM Route setting in the Filr installer must match these values.
Hibernate Caching Provider: memcached is the only option available when configuring Filr in a clustered environment.
For more information about Memcached caching, see Memcached.
Server Address: Each Filr server in the cluster must list all of the Lucene servers (hostname or IP address) in the cluster, with each server separated by a space. For example, lucene_hostname1 lucene_hostname2.
Changes made to one Filr node are immediately visible in other Filr nodes.
Click OK, then click Reconfigure Filr Server for your changes to take effect.
This stops and restarts your Filr server. Because this results in server downtime, you should restart the server at off-peak hours.