5.0 Filr Clustering Configuration

Path: Port 9443 Appliance Console Configuration icon > Clustering

Table 5-1 Using the Clustering dialog

Field, Option, or Button

Information and/or Action

Enable Clustered Environment

  • Click this to enable Filr clustering on this appliance and on all appliances using the same /vashare NFS or CIFS mount point.

  • JVM Route

  • You can leave this field blank unless you plan to use Apache as the reverse proxy.

  • If you plan to use Apache as the reverse proxy, add a JVM route for each Filr Appliance in the Cluster. 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.

    The Search appliance runs the Memcached service to enable clustering. Port 11211 is used by the Memcached service.

    IMPORTANT:To secure Memcached, it is strongly recommended to deploy the Search appliance behind the firewall.

    For more information on securing Memcached, see Securing Memcached.

  • Server Address:

  • The hostnames or IP addresses of both Filrsearch servers, separated by a space.

  • After clicking OK, you must 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 during off-peak hours.