Other pooling operations

Besides the splunk pooling enable CLI command, there are several other commands that are important for managing search head pooling:

• splunk pooling validate
• splunk pooling disable
• splunk pooling display

You must stop splunkd before running splunk pooling enable or splunk pooling disable. However, you can run splunk pooling validate and splunk pooling display while splunkd is either stopped or running.

Validate that each search head has access to shared resources

The splunk pooling enable command validates search head access when you initially set up search head pooling. If you ever need to revalidate the search head's access to shared resources (for example, if you change the NFS configuration), you can run the splunk pooling validate CLI command:

  splunk pooling validate [--debug]

Disable search head pooling

You can disable search head pooling with this CLI command:

  splunk pooling disable [--debug]

Run this command for each search head that you need to disable.

Important: Before running the splunk pooling disable command, you must stop splunkd. After running the command, you should restart splunkd.

Display pooling status

You can use the splunk pooling display CLI command to determine whether pooling is enabled on a search head:

  splunk pooling display

This example shows how the system response varies depending on whether pooling is enabled:

$ splunk pooling enable /foo/bar
$ splunk pooling display
Search head pooling is enabled with shared storage at: /foo/bar
$ splunk pooling disable
$ splunk pooling display
Search head pooling is disabled