Search
Clear search
Close search
Google apps
Main menu

Configuring GSA Mirroring

This guide contains the information you need to use GSA mirroring, a feature of the Google Search Appliance. GSA mirroring is a feature that enables the index and other configuration information from one search appliance, called the master node, to be replicated to another search appliance, called a replica. You can set up either an active-active or active-passive mirroring configuration.

This document is for you if you are a search appliance administrator, network administrator, or another person who configures search appliances or networks. You need to be familiar with the Google Search Appliance and how to configure crawl, serve, and other features.

On the Admin Console, GSA mirroring is configured under Admin Console > GSAn.

Back to top

Introducing GSA Mirroring


GSA mirroring is a feature that enables the index on one search appliance to be replicated to one or more search appliances. In this release, you can set up active-active or active-passive mirroring configurations.

  • Use an active-passive configuration, in which all search queries are directed to the master search appliance, to provide high availability serving.
  • Use an active-active configuration, in which search queries are distributed between the master and mirror search appliances, to provide high capacity serving.

For more information, see See Deciding Which Mirroring Configuration to Use.

After GSA mirroring is enabled, all crawling is performed only by the master search appliance, limiting the load on content servers. The remaining search appliances can serve, but do not crawl. Most administration is performed only on the master search appliance. Configuration information and the index are replicated to the other search appliances in the configuration. All search appliances serve from the same index and corpus.

Requirements for GSA Mirroring

GSA mirroring requires a sustainable 1 MB per second file transfer rate between the master Google Search Appliance and each replica search appliance. To determine whether a network can provide the required file transfer rate, we recommend that you measure the rate by transferring files on your network between the subnets where the search appliances are located. If the file transfer requirement is not met by the network, the mirroring feature might not work as expected.

Your installation must meet the following requirements to participate in a GSA mirroring configuration:

  • All search appliances must be on the same software version. For example, you cannot have one search appliance in the configuration on version 6.4 and another on version 6.8, or one search appliance on 6.2.0.G14 and another on 6.2.0.G36. When you update from one software version to the next, ensure that you update all search appliances in the configuration.
  • All search appliances in the configuration must be licensed for the same document count.
  • The search appliances must be able to contact each other on TCP ports 8000 and 8443 while mirroring is being set up, and any time a change to the mirroring configuration is made.

The search appliance models you have determine which machine is the master and which can be replicas. The primary consideration for choosing the master is that its license count cannot exceed the maximum license limit of the replica search appliance.

Master Search Appliance

Replica Search Appliances

GB-7007

GB-7007
G100
G500

G100

G100
G500
GB-7007 (supported only if license count on the master is less than 10 million)

G500

G500

Back to top

About GSA Mirroring


When GSA mirroring is enabled, the search index and configuration information are mirrored from the master search appliance to the replica nodes. The search appliances are synchronized on a regular basis, with some delay, using checkpoint files that are produced on the master node. The amount of data synchronized among the search appliances depends on the delta between the index on the master search appliance and the indexes on the replica nodes. When the delta is larger, more data is synchronized. Consider the following three scenarios.

In scenario one, two search appliances have been in a mirroring configuration for some time and their indexes are similar and in a comparatively steady state. The indexed content does not change radically. In this situation, the delta between the two search appliances is small. When the two search appliances are synchronized, the checkpoint files are small and the synchronization process takes place quickly.

In scenario two, both search appliances are freshly installed and the content is being crawled for the first time. The master search appliance produces checkpoint files with newly-crawled content. The checkpoint files will be of a moderate size and will take somewhat more time to transfer than in scenario one. However, when the content has been fully crawled, the two search appliances will be in the same steady state as the search appliances in scenario one: the delta between them is small, checkpoint files are small and the synchronization process is rapid.

In scenario three, the master search appliance has fully crawled a corpus of 10 million documents. The replica search appliance is freshly installed. The full set of checkpoint files from the master search appliance must by synchronized by the replica search appliance. A large amount of data is transferred initially. Eventually, the two search appliances reach the steady state of the search appliances in scenario one.

The GSA mirroring diagnostics page on the Admin Console provides information about the current synchronization process.

Most administrative configuration takes place on the master search appliance. Some configuration information and all index data are replicated automatically and continuously to the replicas.

For information about which configuration data is copied to replicas, see Settings that are Copied or Not Copied to the Replica Search Appliances

Only the master search appliance crawls the content, minimizing the load on content servers and the network. The replica search appliances do not crawl the content, but they can serve the index created on the master node.

The master search appliance ensures the consistency of the search experience by gathering and combining relevancy data. The master node mirrors the relevancy data to all replica nodes in the mirroring configuration.

Note that the composite collections feature found under Admin Console > Index > Composite Collections applies only to search appliance unified environments. You cannot use composite collections with GSA mirroring.

The most common GSA mirroring configuration has one master search appliance and one replica. In the following diagram, three search appliances are configured for GSA mirroring. A search appliance designated as a master search appliance has two replicas, Replica 1 and Replica 2.

Back to top

Deciding Which Mirroring Configuration to Use

In this release, you have a choice of how to direct search traffic.

  • To the master search appliance only, in an active-passive configuration. In this configuration, you can manually fail over search traffic to a replica node if the master search appliance fails.
  • To all nodes, in an active-active configuration. In this configuration, all nodes can serve results. You use a load balancer to distribute search requests among the nodes. Ensure that you use a load balancer that supports sticky user sessions, so that the user receives consistent search results.

The process for setting up mirroring on the search appliance is same for both cases. Load balancers are typically used to achieve either configuration.

When the Master Search Appliance Fails in an Active-Passive Configuration

All nodes should be monitored externally and when the master node is not responding, all search traffic should be redirected to the replica node. You can redirect traffic by using a load-balancer, switching the value of the DNS alias to the replica, or using an external application. Users will be reprompted for credentials on the replica node. Changes to user-facing features such as User Added Results will not propagate to other nodes from a replica node. A replica node can be promoted to be a master node, and the new master node can resume crawling and start accepting feeds. For more information on how to do this, see Promoting a Replica Node to Master. For more information on monitoring, see the section “Setting up monitoring” in Design a search solution.

When a Search Appliance Fails in an Active-Active Configuration

All nodes should be monitored externally. When a node in the configuration fails, your response depends on how the load balancer works.

  • If the load balancer redirects traffic automatically from the failed node to nodes that are still running, you do not need to take action.
  • If the load balancer does not redirect traffic automatically, you must configure the load balancer so that search traffic is correctly directed to the running nodes.

When users with existing sessions are directed to a new node, they might have to log in again.

Settings that are Copied or Not Copied to the Replica Search Appliances

The following settings and data are copied from the master to the replica search appliances:

  • Spelling data
  • SAML
  • Connector Manager definitions and configurations
  • Certificate authorities
  • Configuration data except the settings listed below

The following settings and data are not copied from the master to the replica search appliances:

  • Kerberos
  • Connectors (Connector Manager definitions and configurations are copied)
  • Existing feeds
  • GSA host SSL certificates

Back to top

About Security


The Google Search Appliance uses secret tokens and private IP addresses to enforce security within GSA mirroring configurations.

The search appliances in a GSA mirroring configuration authenticate each other using shared secret tokens that you provide during configuration. The shared secret tokens must consist only of printable ASCII characters.

There are no restrictions on the public IP addresses assigned to the search appliances in the configuration beyond a requirement that a search appliance must be able to reach another search appliance’s public IP address on UDP port 500 and on IP protocol number 51 (IPsec AH). IPSec security protocol uses port 500 and AH protocol to build a secure private network between mirrored nodes. ICMP Echo is used for testing public IP address availability. Ports 8000 and 8443 are used for transmitting configurations between appliances.

Configuration and index data are communicated among the search appliances in a GSA mirroring configuration over a virtual private network. When you set up a GSA mirroring configuration, the search appliance automatically assigns private IP addresses and secret tokens to each machine in the configuration. The private IP addresses are in the range 10.0.0.1, 10.0.0.2, 10.0.0.n unless this range conflicts with the public IP address of the search appliance. In that case, a different address range can be used for the private IP addresses.

If you need to manually change the private IP addresses, the following guidelines apply:

  • The search appliance must able to reach another search appliance’s public IP address on UDP port 500 and on IP protocol number 51 (IPsec AH). The master node should be able to access Port 8443 (SSL) on the replica.
  • GRE (Generic Routing Encapsulation) is used to encapsulate the IP packets over the IPsec tunnel. The replica’s IP setup for tunneling can be checked by clicking Update Settings and Perform Diagnostics on the Administration > Network Settings page, but network diagnostics cannot be used to check the private IP of replica.
  • The private IP addresses you choose must conform to the private address space as defined in RFC 1918 and must not overlap with the private address space used by the subnet to which the appliances are connected. For example, if the subnet where the search appliances are deployed uses 10.0.0.0/8, choose the private IP addresses from the 192.168.0.0/24 network. If the 192.168.0.0/24 network is used by the subnet, try the 192.168.1.0/24 range or the 172.16.0.0/12 range.
  • Do not use the private IP address from the 192.168.255.0/24 network.
  • Do not use 127.0.0.0/8.
  • Do not use non-private address space such as 1.0.0.0/8 or 216.239.43.0/24.

Back to top

Using Kerberos with GSA Mirroring


You must configure Kerberos on the master and all mirrored search appliances by using the Search > Secure Search > Universal Login Auth Mechanisms > Kerberos page in the Admin Console. Kerberos keytabs are unique, so ensure that you generate and import different Kerberos keytabs for the master and mirrored search appliances.

When you configure Kerberos on a replica search appliance, use a different Mechanism Name from the one used for the master. The Mechanism Name for the replica will be synchronized automatically with the master’s Mechanism Name. After they are synchronized, the replica’s Mechanism Name will match the master’s Mechanism Name.

If you intend to access the search appliance using a URL such as http://gsa.yourdomain.com, where the DNS A record is gsa.yourdomain.com, the SPN specified during keytab generation should be HTTP/gsa.yourdomain.com@YOURDOMAIN.COM. During typical operations, gsa.yourdomain.com should point to the master GSA. If you need to make a mirror search appliance the master search appliance, gsa.yourdomain.com should point to the mirror. Because the same keytab and name are used, IWA serving functions normally. If you attempt to perform a secure search on a mirror without the DNS switch (for example, using the IP address or other DNS name), the search fails if the additional SPN is not defined for the search appliance’s account in Active Directory. Additional information about Kerberos and troubleshooting search appliance issues can be found in the search appliance Knowledge Base.

Back to top

Using Certificates with GSA Mirroring


You must set up CA certificate use in the mirroring configuration in one of the two following ways:

  • No search appliances use CA certificates.
  • All search appliances use CA certificates. In this case, the same CA certificate does not need to be installed on all search appliances. However, all search appliances must have CA certificates whose signatures cover the set of certificates used by all search appliances in the configuration.

Back to top

Before You Configure GSA Mirroring


This section provides a checklist of information you need to collect and decisions you need to make before you configure GSA mirroring.

Task

Description

Your Values

Determine whether you are configuring an active-active or active-passive configuration.

Use an active-active configuration for high capacity serving. Use an active-passive configuration for high availability.

 

Determine which Google Search Appliance will participate in the configuration.

Google Search Appliances running the same software version can participate. See the table in Requirements for GSA Mirroring for information about which Google Search Appliance models can be used as master or replica search appliances in the configuration.

 

Determine the appliance IDs of the participating search appliances

You view the appliance IDs on the Admin Console by right-clicking the About link at the bottom of any page and choosing Open in New Tab, or by navigating to Administration > License.

 

Confirm that all search appliances are running the same software version.

You view the software version on the Admin Console by right-clicking the About link at the bottom of any page and choosing Open in New Tab.

 

Confirm that all search appliances are licensed for the same document count.

Review the license terms.

 

Determine the host names or public IP addresses of the search appliances in the configuration.

The host names or IP addresses are required during the initial configuration process.

 

Determine which search appliance is the master search appliance in the configuration.

The master search appliance is the search appliance whose index is replicated to the other nodes.

 

If you are using self-signed SSL certificates, make sure that you install the correct root certificate authorities on the Admin Console, on the page Administration -> Certificate Authorities.

If the wrong root certificate authorities are installed, you see errors and results are not returned properly on replica appliances in an GSA mirroring configuration.

 

If you are using SSL certificates, ensure that they are configured on the master search appliance and on all replicas.

   

Ensure that the certificate configuration is correct.

Either none of the search appliances in the configuration use certificates or all use certificates. See Using Certificates with GSA Mirroring for more information.

 

Back to top

Configuring GSA Mirroring


Use these instructions to configure GSA mirroring. Ensure that you complete all the steps.

To configure the current search appliance as a master node, add its replica appliances, and push the mirroring configuration to all the added replica appliances:

  1. On the master node, log in to the Admin Console.
  2. Ensure that crawling, serving, and security are correctly set up.
  3. Click GSAn > Configuration.
  4. Under GSA Mirroring Administration, click Enable. The current search appliance is designated a master appliance. The network IP address and secret token are automatically assigned.
  5. To add a mirror for the current search appliance, type the GSA Appliance ID, Appliance hostname, Admin Username, and Password under the section Please enter the configuration information for the node.

    If Admin NIC is enabled on the node that you are adding, use the IP address or hostname of the primary NIC for the Appliance Hostname, click Admin NIC enabled on remote node? and type the IP address of the remote node’s Admin NIC in Admin NIC IP Address.

  6. Check Enable (if not checked by default).
  7. Click Done or Add Another Replica.
  8. Optionally, click Export and save the mirroring configuration file.
  9. On your replica (mirror) search appliance, log in and perform the following steps.
  10. Right-click the About link, choose Open in New Tab, and confirm that the replica node is on the same software version as the master search appliance.
  11. Click Status and Reports. The Crawl Status page is displayed.
  12. Click Pause Crawl.
  13. Click Index > Reset Index.
  14. Click Reset the Index Now.
  15. Wait until the reset index process has completed and the values under Crawl Status on the Content Sources > Diagnostics > Crawl Status page are 0.
  16. Repeat steps 9 to 15 on each additional mirror node.
  17. On the master node, click Apply Configuration on the GSAn > Configuration page. This broadcasts the configuration data to all search appliances in the GSAn network. Note that document serving will be interrupted briefly on the master node after you click Apply Configuration.

Because the search appliances in a GSAn configuration continuously attempt to re-establish the connection between nodes, there is no specific action required if you reboot a node or take it offline.

Adding a New Replica to an Existing Master Node

After you configure GSA mirroring, you can perform the following procedure at any time to add a new replica to an existing master node.

  1. On the master node, log in to the Admin Console.
  2. Click GSAn > Configuration.
  3. Click the View/Edit link for the shard where you want GSA mirroring enabled.
  4. To Add a Node to this shard, click Add.
  5. On the drop-down list, choose Replica.
  6. Type in the replica node’s GSA Appliance ID.
  7. Type in the Appliance hostname or the IP address of the search appliance.
  8. Type in the Admin username and Password.
  9. Type in the Network IP of the search appliance.

    The Network IP should be in the same subnet as your other search appliances.

  10. If Admin NIC is enabled on the replica that you are adding, click Admin NIC enabled on remote node? and type the IP address of the replica in IP Address.
  11. Check Enable.
  12. Click Save.
  13. Optionally, click Export and save the configuration file to the local computer.
  14. Log in to the new replica search appliance.
  15. Right-click the About link, choose Open in New Tab, and confirm that the replica node is on the same software version as the master search appliance.
  16. Click Content Sources > Diagnostics > Crawl Status.
  17. Click Pause Crawl.
  18. Click Index > Reset Index.
  19. Click Reset the Index Now.
  20. On the GSAn > Configuration page for the master node, click Apply Configuration. This broadcasts the configuration data to all search appliances in the GSAn network. Note that document serving will be interrupted briefly on the master node after you click Apply Configuration.

Setting Network Bandwidth for GSAn

If you have limited bandwidth or a large amount of data to transfer between the master search appliance and replica nodes, you can adjust the file transfer rate. The default rate is 40 megabytes per second. The valid range is 1 to 512.

To change the maximum transfer rate:

  1. Log in to the Admin Console.
  2. Click GSAn > Configuration. The existing configuration details are displayed.
  3. In the Maximum transfer rate for GSAn field, enter the maximum transfer rate, in megabytes per second.
  4. Click Save.
  5. Click Apply Configuration.

Note: Setting this value too high can cause network issues in your LAN environment.

Back to top

Setting the Default Search URL in a GSA Mirroring Configuration


In a mirroring configuration, the default search URL is specified using a relative URL. Whether you are setting up GSA mirroring for the first time or updating the default search URL in an existing mirroring configuration, change the default search URL on the master and the replica search appliances. The default search URL on the master search appliance is not replicated to the replica search appliances.

For example, assume that you have one search appliance, gsa1, that you use for search. The default search URL for gsa1 is

http://gsa1/search?site=default_collection&client=
default_frontend&proxystylesheet=default_frontend&proxycustom=%3CHOME/%3E

If you add a second search appliance, gsa2, and configure mirroring, you must change the default search URL on the master search appliance to

/search?site=default_collection&client=default_frontend&proxystylesheet=
default_frontend&proxycustom=%3CHOME/%3E

To change the default search URL:

  1. On the master search appliance, log in to the Admin Console.
  2. Click Administration > System Settings.
  3. Type the new default search URL in the Default Search URL field.
  4. Click Update System Settings.

Alternatively, you can also set up a single round-robin DNS record for all nodes, so that every search appliance (master or replica) can be accessed via the same host name. In this case, you can set the default URL to point to the shared hostname.

Back to top

Tasks Performed on Replica Search Appliances


After GSA mirroring is configured, you perform most administrative tasks only on the master search appliance. The following administrative tasks are performed on the replica search appliances:

  • Installing a new license. All search appliances in the mirroring configuration must be licensed for the same document count.
  • 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.
  • Importing x509 certificates, whether CA or certificates for the search appliance
  • Setting the URLs in the following fields on the Search > Secure Search > 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 Cloud 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.

Back to top

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.

Back to top

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.
  2. In a text editor, open the file server.xml.
  3. Locate the Valve class and add the IP address of the replica search appliance to the RemoteAddressValve property. This enables the connector manager to respond to requests coming from the replica node. For example:
    Valve className="org.apache.catalina.valves.RemoteAddrValve"
    allow="127\.0\.0\.1|172\.25\.17\.88|172\.25\.16\.144|
    pattern_for_replica_IP_address"

    For more information, see the Apache Tomcat Valve documentation (http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html#Remote_Address_Filter)

  4. On the Admin Console of the replica node, navigate to the connector manager page. The icon for the connector manager turns green within a few minutes, and the connector instance is displayed shortly after.
  5. Perform a secure search from the replica node.
  6. Examine the connector manager logs, which should show that the authorization request was sent through the connector instance.

If your master search appliance fails and you must make a replica node the master node, use these instructions to force the external connector manager to send feeds to the new master node.

To direct feeds to the new master node:

  1. On the connector manager host, navigate to connector_directory/connector_manager_name/Tomcat/webapps/connector-manager/WEB-INF.
  2. In a text editor, open the file applicationContext.properties.
  3. Locate the entry gsa.feed.host=.
  4. Change the value to the IP address of the new master node.
  5. Restart the connector manager service for changes to take effect.

Back to top

Promoting a Replica Node to Master


Promote a replica node to the master node in a GSA mirroring configuration only when the master node fails and is not accessible. After promotion, the new master node begins crawling where the old master node stopped its crawl. In addition, port 19900 on the master begins to accept feeds.

If your installation includes connectors, see Configuring Connectors with GSA Mirroring for information on sending content from connectors to the new master node.

The process of promoting a search appliance from replica to master in a mirroring configuration depends on how many nodes are in the configuration.

  • When the master node in a two-node configuration fails, you disable mirroring and the replica becomes an individual search appliance with no mirror node.
  • When the master node in a three-or-more-node configuration fails, any replica can be promoted to master. You can then re-enable mirroring with the remaining nodes.

If the master Google Search Appliance fails and a replica search appliance is promoted to be the master, do not directly add the former master node back as the master, because this will cause problems in the mirroring configuration. If you need to use the former master search appliance as the master, add it as a replica of the new master first. Wait until all index and configuration data are fully synchronized with the new master node, and then you can add the search appliance as the master again.

To promote a replica node to master when there is only one replica node in the configuration:

  1. Log in to the Admin Console of the replica node.
  2. Navigate to the GSAn > Configuration page and click Disable GSAn.
  3. Wait approximately 15 to 30 minutes for the Crawl Diagnostics content to display.
  4. Click Content Sources > Diagnostics > Crawl Status.
  5. Click the Resume Crawl button. The node is configured as an individual search appliance.

To promote a replica node to master when there are two or more replica nodes:

  1. Log in to the Admin Console of each replica node and perform steps 2 to 6 on each replica.
  2. Click Content Sources > Diagnostics > Crawl Status.
  3. Click the Pause Crawl button.
  4. Navigate to the GSAn > Configuration page and click Disable GSAn.
  5. Wait approximately 15 to 30 minutes.
  6. Examine the Crawl Diagnostics page to see whether it is displaying indexed URL content on all replica nodes.
  7. Log in to the Admin Console of the node you are promoting to the master node.
  8. Navigate to the GSAn > Configuration page and click Enable.
  9. Configure the remaining search appliances as replica nodes.
  10. On the new master node, click Content Sources > Diagnostics > Crawl Status.
  11. Click the Resume Crawl button.

Back to top

Deleting Replica Nodes from an Existing GSA Mirroring Configuration


Use these instructions to remove a node from an existing mirroring configuration.

To delete a replica node from a mirroring configuration:

  1. Log in to the Admin Console of the master node.
  2. Click GSAn > Configuration.
  3. Click the View / Edit link.
  4. Click the Remove link that corresponds to the replica you are deleting from the configuration.
  5. Click Apply Changes.
  6. Log in to the Admin Console of the replica node.
  7. Click GSAn > Configuration.
  8. Click Disable GSAn. The Crawl Diagnostics page is not available for approximately 15 minutes after you disable GSAn.

Back to top

Disabling Mirroring on an Existing Replica Node


Use these instructions to disable mirroring from the master node to a replica node. The mirroring configuration still exists but data is not mirrored from the master node to the replica.

To disable mirroring an existing replica node:

  1. Log in to the master search appliance.
  2. Navigate to GSAn > Configuration.
  3. Locate the replica node you want to disable.
  4. Uncheck the Enable check box.
  5. Click Apply Configuration. The change is propagated to the replica node and data is not mirrored until you check the check box again. Note that document serving will be interrupted briefly on the master node after you click Apply Configuration.

Back to top

GSA Mirroring Diagnostics


The GSA mirroring feature includes diagnostic information specific to the feature. The diagnostic information is displayed under Admin Console > GSA n> Diagnostics on the master node only. If you try to access the page on a mirror node, you see only the connection status of nodes on the GSAn network.

The following table describes the diagnostic information.

Label

Explanation

Node

Google Search Appliance host name.

Peer Status

Shows the current status of the multibox configuration: Config Sync, UP, or DOWN for Master; Non-Master (Distributed Crawling) Setup and N/A for Master-Replica (Mirroring) Setup.

Current Time

The current date and time, for example: 2011/02/17 11:35.

Last Config Sync Completed

The date and time when the administrative configuration was most recently synchronized from the master node to the replica nodes; for example, 2010/01/08 16:46.

Serving Index Creation Time

The date and time when the currently-serving search index was created; for example, 2010/01/08 16:41.

Serving Index Sync Completion Time

The date and time when the currently-serving index on a node was synchronized; for example, 2010/01/08 16:42.

Serving Index Sync Time

The amount of time it took for the currently-serving index to be completely synchronized from the master to the replica nodes; for example, 0h 30m.

Syncing Index Creation Time

The date and time when the index that is currently being synchronized was created; for example, 2010/01/10/17:14.

Syncing Index Transfer Progress

The percentage of the current synchronization process that is completed; for example, 16%.

Syncing Index Transfer Speed

The transfer speed of the current synchronization process, in kilobytes per second; for example, 801 KB/sec.

Syncing Index Estimated Completion Time

The estimated total amount of time required to complete the current synchronization process; for example, 0h 42 m. This estimate is based on the transfer speed and not on the current progress. It represents an estimate of how long the full synchronization process will take, not the remaining time before the process is complete. To calculate the time to completion, use the formula (100% - transfer_progress * estimated_completion_time), substituting the displayed values for transfer_progress and estimated_completion_time.

After you click Apply Configuration while configuring GSA mirroring, the search appliance takes up to two minutes to complete all background processes. The network diagnostics page is not automatically refreshed after all processing is complete. Wait two minutes, then refresh the browser by clicking its Refresh button. You should see green indicators at that time.

Back to top

Was this article helpful?
How can we improve it?