<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How does the splunk search works? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-does-the-splunk-search-works/m-p/172027#M49312</link>
    <description>&lt;P&gt;The key for distributing the search over your indexers is the data. If one indexer has twice as much data that matches a search it'll do twice as much work for that particular search.&lt;/P&gt;

&lt;P&gt;With your example, each indexer will search all its data on its own and produce a pre-computed stats result (map phase - see the job inspector for the remoteSearch) and the searchhead will produce the overall stats result (reduce phase - see the reportSearch in the job inspector).&lt;/P&gt;

&lt;P&gt;Small performance niggle I can't keep to myself:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| tstats values(source) where index=* by host
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That will be miles faster &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 20 May 2014 17:54:59 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2014-05-20T17:54:59Z</dc:date>
    <item>
      <title>How does the splunk search works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-the-splunk-search-works/m-p/172025#M49310</link>
      <description>&lt;P&gt;When i enter a search query , say (index=* | stats values(source) by host)&lt;BR /&gt;&lt;BR /&gt;
How does this fetch the data from the indexer ?&lt;BR /&gt;&lt;BR /&gt;
when I have 2 or more indexer , how does the search is splited across the indexers to get the results ?&lt;BR /&gt;&lt;BR /&gt;
Is there a flow diagram with process names to get a view ?&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2014 15:00:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-the-splunk-search-works/m-p/172025#M49310</guid>
      <dc:creator>splunker12er</dc:creator>
      <dc:date>2014-05-20T15:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: How does the splunk search works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-the-splunk-search-works/m-p/172026#M49311</link>
      <description>&lt;P&gt;You could read the book &lt;A href="http://www.splunk.com/goto/book"&gt;Exploring Splunk&lt;/A&gt;, by David Carasso.&lt;/P&gt;

&lt;P&gt;There is also an article about &lt;A href="http://www.splunk.com/web_assets/pdfs/secure/Splunk_and_MapReduce.pdf"&gt;Splunk and MapReduce&lt;/A&gt;.&lt;/P&gt;

&lt;P&gt;But how the search runs across the indexers is managed entirely by Splunk - the user does not do (or even see) anything different, regardless of the number of indexers. The Splunk Admin sets up distributed search, but even that does not specify how individual searches are run - again, that is managed by Splunk.&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2014 16:38:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-the-splunk-search-works/m-p/172026#M49311</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-05-20T16:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: How does the splunk search works?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-the-splunk-search-works/m-p/172027#M49312</link>
      <description>&lt;P&gt;The key for distributing the search over your indexers is the data. If one indexer has twice as much data that matches a search it'll do twice as much work for that particular search.&lt;/P&gt;

&lt;P&gt;With your example, each indexer will search all its data on its own and produce a pre-computed stats result (map phase - see the job inspector for the remoteSearch) and the searchhead will produce the overall stats result (reduce phase - see the reportSearch in the job inspector).&lt;/P&gt;

&lt;P&gt;Small performance niggle I can't keep to myself:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| tstats values(source) where index=* by host
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That will be miles faster &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2014 17:54:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-the-splunk-search-works/m-p/172027#M49312</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-05-20T17:54:59Z</dc:date>
    </item>
  </channel>
</rss>

