Deploying multiple Collection Stations and Indexers
In large setups, with growing needs for indexing large volumes of data, the Collection Station and Indexer (and sometimes Search) might need to be deployed and scaled on separate servers. In these setups, you can separate the collection and indexing functions of the product. You can either deploy the Collection Station on one server and the Indexer on server host, or you can deploy both the Collection Station and Indexer on the same server. As you scale, you can continue adding these components on additional servers. For more information about when to scale, see Indicators-for-scaling.
When you scale Indexers, you need to provide details of the master Indexer installed on the primary node. Data collected and searched is distributed across all the Indexers available. For more information about how Indexers function in a multiple-server deployment, see Indexer-redundancy.
This topic contains the following information:
Deployment diagram
The following diagram illustrates the scale-out architecture for Collection Stations and Indexers.
Where to go from here
To deploy multiple Collection Stations and Indexers, 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.
(Optional) You might want to move data collectors from one Collection Agent (or Collection Station) to another. For more information, see movecollectors-CLI-command.