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.
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
Use a load balancer with the search head pool | Manage configuration changes |
This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9
Feedback submitted, thanks!