Community:How to add a search head to your pool

From Splunk Wiki

Jump to: navigation, search

This document is for pre-4.2 Splunk. After 4.2 is released, we introduced a search head pooling. For more detail, please visit our online document.

This page details how to add an additional search head to your existing distributed deployment. These instructions assume that you are a qualified Splunk administrator and have previously deployed Splunk instances. In this exercise, we will assume we have many indexers and two search heads. For reference purposes, we will call each of N indexers indexer01, indexer02, and similar. The search heads will be referenced as searcher01 and searcher02. The existing example deployment consists of N indexers, with searcher01 searching the N indexers.

  1. Install Splunk on the search head (searcher02)
  2. To leverage similar password capabilities, distribute the same splunk.secret file and the same ssl password key.
    1. Copy the opt/splunk/etc/auth/splunk.secret file from searcher01 to the same location on searcher02
    2. Copy the sslKeysfilePassword parameter in the [sslConfig] stanza of the /opt/splunk/etc/system/local/server.conf file of searcher01 to searcher02
  3. Distribute the authentication token from the search head to each indexer
    1. Copy the /opt/splunk/etc/auth/distServerKeys/trusted.pem file from searcher02 to /opt/splunk/etc/auth/distServerKeys/searcher02/trusted.pem on each indexer
    2. As an alternative, you could use the UI to do this which will also add them to the local distributed configuration (distsearch.conf)
  4. Copy the relevant configuration files
    1. To retain similar user configuration, copy the relevant user files
  • $SPLUNK_HOME/etc/passwd
  • $SPLUNK_HOME/etc/authentication.conf
  • $SPLUNK_HOME/etc/authorize.conf
  • $SPLUNK_HOME/etc/users (copy the whole directory, as this retains the user data)
    1. To retain similar functionality within each app (search), copy the respective /local configuration
  • $SPLUNK_HOME/etc/apps/search/local
    1. To retain similar system level functionality, copy other system files from searcher01 to searcher02 EXCEPT for the following. You should instead MANUALLY add the configurations via edits. This is because the server/hostnames will be different.
  • $SPLUNK_HOME/etc/system/local/inputs.conf
  • $SPLUNK_HOME/etc/system/local/server.conf
Personal tools
Hot Wiki Topics

About Splunk >
  • Search and navigate IT data from applications, servers and network devices in real-time.
  • Download Splunk