topic Re: adding new indexer in existing distributed environment in Getting Data In

adding new indexer in existing distributed environment

ramsanga — Mon, 07 Jul 2014 11:30:43 GMT

i currently have one indexer and two search heads with one search head with ES. I am planning to add two new indexers in existing setup for load balance and convert existing indexer into heavy forwarder. I am sure i can copy existing indexed DB to one of the newly to be deployed indexer, stop indexing in old indexer and configuring forwarding only . My question is how can i achieve load balance in new setup retaining old indexed data.

Re: adding new indexer in existing distributed environment

sourabh_varshne — Mon, 07 Jul 2014 11:51:09 GMT

Once you add up the two indexers , your new environment will have two indexers, two search heads and one heavy forwarder. Now to enable load balancing follow the below steps.

Enable load balancing at Heavy Forwarders by editing outputs.conf autoLBFrequency = 40 server = \ips of indexers useACK = true
Increase queue size maxQueueSize = 100 MB

This will enable load balancing of data at your indexers. Also enable replication between both of your indexers. Hope this answers your question

Re: adding new indexer in existing distributed environment

ramsanga — Mon, 07 Jul 2014 11:56:18 GMT

thanks for your answer on LB side. I wanted to know the best way to copy old indexed data into two new indexer so that i can search old data. I read the article http://answers.splunk.com/answers/6521/expanding-splunk-installation-from-a-single-indexer-to-a-multi-indexer-dedicated-search-head-environment
does this work?

Re: adding new indexer in existing distributed environment

sourabh_varshne — Mon, 07 Jul 2014 12:12:41 GMT

Yes you can follow that link. Its perfectly demostrated. You can copy buckets directl and restart your cluster.

Re: adding new indexer in existing distributed environment

ramsanga — Mon, 07 Jul 2014 16:27:01 GMT

Thanks sourabh. Just wrt your comment earlier, can replication be enabled with two indexer. According to document, we need one seperate master node and then at least two peer nodes for replication (clustering).please advise..In addition. will replication not not cause low search and indexing performance?