Search
Clear search
Close search
Google apps
Main menu

Managing the load for multiple connectors on the same host

Summary:

In some cases you may need to start multiple Connector 4 instances on one server (e.g., several instances of the SharePoint connector to crawl different site collections). Administrators may want to configure the GSA to mitigate excessive load on content servers and prioritize crawling for one of the connectors.

The goal is to configure host load so the content is actively crawled by one or a set of the connectors.

Cause:

The GSA uses the host load feature to control load on content servers that need to be configured in a specific way to balance the load.

Fix:

The idea is to split the host load between connectors and add the sum of the host load for the IP address of the connector host server.

Example:

You have three connectors to crawl SharePoint, Filesystem, and Database content from one connector host. Connectors are configured to run on different ports:

  1. SharePoint: http://connector.example.local:1111/
  2. Filesystem: http://connector.example.local:2222/
  3. Database: http://connector.example.local:3333/

You want to prioritize SharePoint connector crawling.

Let's assume that connector host name resolves to 11.12.13.14 and you want to allow four concurrent connections on the SharePoint connector, but limit the Filesystem and Database connectors to only to one concurrent connection.

To configure the GSA as described, perform the following steps in the Admin Console:

  1. Open the Content Sources > Web Crawl > Host Load Schedule page
  2. Set host load 4.0 for SharePoint http://host.example.com:1111/ pattern
  3. Set host load 1.0 for Filesystem http://host.example.com:2222/ pattern
  4. Set host load 1.0 for Database http://host.example.com:3333/ pattern
  5. Set host load 6.0 (4 + 1 + 1) for 11.12.13.14 IP

In general, the IP host load should be the SUM of all individually configured host loads.

Screenshot from Host Load page in Admin Console:

Additional Details: For more details about configuring host load, see About the Load on the Web Server Host

Was this article helpful?
How can we improve it?