Deploying multiple Search components
In large setups with large volumes of indexed data and numerous concurrent users searching on the data, the Search component might need to be deployed and scaled on separate servers. In these setups, the Search components can reside on separate servers that handle only the search function of the product. For more information about when to scale, see Indicators-for-scaling.
In a multiple-server deployment, the Search component sends search requests to the Indexer. The Indexer performs actual searches on the indexes, which are then rolled back in the form of search results. Scaling the Search component helps you distribute the searching load across multiple instances, which in turn helps you search large quantities of data.
This topic contains the following information:
Deployment diagram
The following diagram illustrates the scale-out architecture for Search components. This diagram only shows the Search component scaled. In a real environment, when you scale up the Search component, you might have Collection Stations and Indexers scaled up.
Where to go from here
To deploy multiple Search components, you need to first install them. For more information, see Installing-in-a-multiple-server-environment.
If you initially installed the product by performing a typical installation and want to scale the product on additional servers, then you need to make certain configuration changes. For more information, see Configurations-required-before-scaling-up.