Heavy and light forwarder capabilities
Certain capabilities are disabled in heavy and light forwarders. This section describes forwarder capabilities in detail.
Splunk heavy forwarder details
The heavy forwarder has all Splunk functions and modules enabled by default, with the exception of the distributed search module. The file
$SPLUNK_HOME/etc/apps/SplunkForwarder/default/default-mode.conf includes this stanza:
[pipeline:distributedSearch] disabled = true
For a detailed view of the exact configuration, see the configuration files for the SplunkForwarder application in
Splunk light forwarder details
Most features of Splunk are disabled in the Splunk light forwarder. Specifically, the Splunk light forwarder:
- Disables event signing and checking whether the disk is full (
- Limits internal data inputs to
splunkdand metrics logs only, and makes sure these are forwarded (
- Disables all indexing (
- Does not use
transforms.confand does not fully parse incoming data, but the
CHARSET, CHECK_FOR_HEADER, NO_BINARY_CHECK, PREFIX_SOURCETYPE,and
- Disables the Splunk Web interface (
- Limits throughput to 256KBps (
- Disables the following modules in
[pipeline:indexerPipe] disabled_processors= indexandforward, diskusage, signing,tcp-output-generic-processor, syslog-output-generic-processor, http-output-generic-processor, stream-output-processor [pipeline:distributedDeployment] disabled = true [pipeline:distributedSearch] disabled = true [pipeline:fifo] disabled = true [pipeline:merging] disabled = true [pipeline:typing] disabled = true [pipeline:udp] disabled = true [pipeline:tcp] disabled = true [pipeline:syslogfifo] disabled = true [pipeline:syslogudp] disabled = true [pipeline:parsing] disabled_processors=utf8, linebreaker, header, sendOut [pipeline:scheduler] disabled_processors = LiveSplunks
These modules include the deployment server (not the deployment client), distributed search, named pipes/FIFOs, direct input from network ports, and the scheduler.
The defaults for the light forwarder can be tuned to meet your needs by overriding the settings in
$SPLUNK_HOME/etc/apps/SplunkLightForwarder/default/default-mode.conf on a case-by-case basis.
Purge old indexes
When you convert a Splunk indexer instance to a lightweight forwarder, among other things, you disable indexing. In addition, you no longer have access to any data previously indexed on that instance. However, the data still exists.
If you want to purge that data from your system, you must first disable the SplunkLightForwarder app, then run the CLI
clean command, and then renable the app. For information on the
clean command, see "Remove indexed data from Splunk" in the Admin manual.
Deploy a heavy or light forwarder
What is distributed search?
This documentation applies to the following versions of Splunk® Enterprise: 4.3, 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7