How distributable and non-distributable commands work in Hunk (and what works best)
Distributable search commands are more effective in Hunk because they can be distributed to search heads and virtual indexes. Generally, non-distributable commands only work on local indexes and are not as effective on virtual indexes.
You can create searches across different index types that use both distributable and non-distributable commands as long as you keep in mind that these such a search returns all data from the local indexes but limited data from the virtual indexes.
This topic discusses the types of commands that work best with Hunk and commands that should be reserved for use with the Splunk Enterprise local directories.
Smart mode searches
Search modes control the amount or type of data that the search returns.
Smart mode is the default and recommended setting for VIX searches. It maintains search behavior based on whether your search contains transforming commands. When searching virtual indexes we recommend that you search in smart mode, as it is more efficient.
If you use verbose mode to search a VIX, note that Hunk does not start a MapReduce job for that search. This is because verbose mode searches search for all events as well as any reports that you might be running. The benefits of MapReduce jobs in that case are minimal and in some cases can have a negative impact on your searches.
To learn more about Splunk Enterprise search modes, see In the Search Manual:
Distributable commands are commands that can be run on a local indexer but can also be distributed to search heads and virtual indexes. They run on the indexer in Enterprise and the DataNode/TaskTracker in Hunk.
Commands that work best with virtual indexes are:
- Distributable streaming commands: This is any streaming command that operates on each event returned by a search. Distributable streaming commands include:
- Distributable generating commands: Event-generating commands that are distributable return an events list or a table of results. Generating commands are usually invoked at the beginning of the search and with a leading pipe. There cannot be a search piped into a generating command. (The exception is the search command, because it is implicit at the start of a search and does not need to be invoked.) Distributable event-generating commands include:
Non-distributable (also referred to as non-streaming) commands require all data to come back to the local indexer. They are not particularly effective commands for searching virtual indexes.
Non-streaming commands are best reserved for when part of your searching involves local indexes in some capacity. Searches run across local and virtual indexes that use non-distributable commands will be applied to local indexes but not the virtual indexes included in the search.
Types of non-distributable or non-streaming commands are:
- Centralized streaming commands: These commands are sometimes referred to as "stateful streaming" commands and include:
- Transforming streaming commands: A transforming command orders events into values that Splunk can use for statistical purposes and include:
- Non-distributable Generating commands: Generating commands that are either centralized event-generating or report-generating do not work on virtual indexes.
Note: You cannot export data from any searches that contain any reporting commands.
There are a handful of commands that do not fit into these categories. These commands are non-reporting, not distributable, and not streaming: sort, eventstats, some modes of dedup, and some modes of cluster.
Configure your HDFS source
Header extractions that do not work in Hunk
This documentation applies to the following versions of Hunk®(Legacy): 6.0, 6.0.1, 6.0.2, 6.0.3, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.2, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11