<?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 search head pooling work with scheduled searches? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75815#M19164</link>
    <description>&lt;P&gt;Whichever search head happens to acquire a lock on a job instance first, they'll run it. So, no, there isn't a lot of intelligence behind it. If a machine is running slower (and assuming clocks are all in sync), then it will be slightly less likely to pick up a job, but that's about it.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Sep 2011 22:51:41 GMT</pubDate>
    <dc:creator>gkanapathy</dc:creator>
    <dc:date>2011-09-14T22:51:41Z</dc:date>
    <item>
      <title>how does search head pooling work with scheduled searches?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75814#M19163</link>
      <description>&lt;P&gt;i like the idea of search head pooling with respect to ease of managing configs across multiple search heads.  but i'm a little confused as to how scheduled searches are divvied between the search heads in the pool.  is there any logic behind it?  will it work intelligently if i have non-homogeneous HW for my search heads?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2011 22:18:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75814#M19163</guid>
      <dc:creator>tpsplunk</dc:creator>
      <dc:date>2011-09-14T22:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: how does search head pooling work with scheduled searches?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75815#M19164</link>
      <description>&lt;P&gt;Whichever search head happens to acquire a lock on a job instance first, they'll run it. So, no, there isn't a lot of intelligence behind it. If a machine is running slower (and assuming clocks are all in sync), then it will be slightly less likely to pick up a job, but that's about it.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2011 22:51:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75815#M19164</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-09-14T22:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: how does search head pooling work with scheduled searches?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75816#M19165</link>
      <description>&lt;P&gt;are there any plans on the roadmap to set or influence which search head(s) in the search head pool run scheduled searches?  I'd like to do this so i can have search head dedicated for ad-hoc searches and others for scheduled searches and still get the ease of maintenance you get with pooling search heads.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2011 23:54:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75816#M19165</guid>
      <dc:creator>tpsplunk</dc:creator>
      <dc:date>2011-09-14T23:54:31Z</dc:date>
    </item>
    <item>
      <title>Re: how does search head pooling work with scheduled searches?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75817#M19166</link>
      <description>&lt;P&gt;We have 5 seachheads in our pool.  1 is dedicated to running scheduled searches.  The others do NOT run scheduled searches.  On the searchheads that you DON'T want to run scheduled searches, in .../splunk/etc/system/local in default-mode.conf add:&lt;BR /&gt;
[pipeline:scheduler]&lt;BR /&gt;
disabled = true&lt;/P&gt;

&lt;P&gt;We had to do this locally on each searchhead because "disabled=false" doesn't work.&lt;/P&gt;

&lt;P&gt;Basically you are setting up a single server as a Splunk jobs server.&lt;/P&gt;</description>
      <pubDate>Thu, 17 May 2012 12:59:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/how-does-search-head-pooling-work-with-scheduled-searches/m-p/75817#M19166</guid>
      <dc:creator>rmorlen</dc:creator>
      <dc:date>2012-05-17T12:59:52Z</dc:date>
    </item>
  </channel>
</rss>

