Google Search Appliance Configuring GSA Mirroring version 7.0 - Manual (Page 13)

Google Search Appliance: Configuring GSA Mirroring 13
• Configuring the IP address and other tasks that must be performed from the Network
Configuration wizard
• Configuring Kerberos settings. For complete information, see “Using Kerberos with GSA Mirroring”
on page 9.
• Importing x509 certificates, whether CA or certificates for the search appliance
• Setting the URLs in the following fields on the Serving > Access Control panel:
• User Login URL
• Artifact Service URL
• Authorization Service URL
Do not perform any other tasks on the replica search appliances unless you are requested to do so by
Google Enterprise Technical Support representatives.
After GSA mirroring is configured, you can view crawl diagnostics and content statistics only on the
master node. On the replica nodes, you see error messages.
In an active-active serving scenario, search queries performed on replica appliances are combined into
the master appliance’s search logs and search reports. A search log or generated search report on a
replica appliance only contains data gathered from that individual appliance.
Since these search logs and search reports are not replicated between appliances, if you need to save
search logs or generated reports, export them periodically or send them to a syslog server. For
additional information, see the search appliance help system topics on logs, reports, and syslog servers.
Setting Up Feeds in a Mirroring Configuration
In a mirroring configuration, send feeds only to the master node. On the replica nodes, feeds are not
accepted, because port 19900 is not available. Unprocessed feeds are not replicated to replica nodes, so
if the master node is down and a replica node is made a master, unprocessed feeds must be re-sent to
the new master node.
Configuring Connectors with GSA Mirroring
You can use Google Search Appliance connectors with GSA mirroring. If you use a connector, Google
recommends that you use an external connector manager and connector, installed on a separate host
computer, rather than the internal connector. For information about using external connectors, see the
appropriate connector documentation. If you are using an internal connector, you encounter the
following issues.
• If the master node fails and you must enable a replica as the new master node, the connector must
retraverse the repository. This is because the connector state and checkpoints are not propagated
from the master search appliance to the replicas.
• In a mirroring configuration, the internal connector configuration is propagated from the master
node to the replicas. This enables the traversal process, increasing the load on your content servers.
However, the replica nodes are unable to receive feeds.
To use an external connector in a mirroring configuration:
1. On the connector manager host, navigate to connector_directory/connector_manager_name/Tomcat/
conf.