<?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: splunk-optimize in multi-instance enviroments in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63950#M22376</link>
    <description>&lt;P&gt;you might want to open a case to splunk support to see if they have a suggestion&lt;/P&gt;</description>
    <pubDate>Tue, 18 Sep 2012 20:01:11 GMT</pubDate>
    <dc:creator>MarioM</dc:creator>
    <dc:date>2012-09-18T20:01:11Z</dc:date>
    <item>
      <title>splunk-optimize in multi-instance enviroments</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63947#M22373</link>
      <description>&lt;P&gt;I have an architecture that houses many individual instances of splunk.  Occasionally splunk-optimizes will run at the same time for many instances.  This causes load spikes.  Is there any way to stagger or control when splunk optimizes are run on a per instance basis.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2012 18:31:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63947#M22373</guid>
      <dc:creator>jfraiberg</dc:creator>
      <dc:date>2012-09-18T18:31:42Z</dc:date>
    </item>
    <item>
      <title>Re: splunk-optimize in multi-instance enviroments</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63948#M22374</link>
      <description>&lt;P&gt;You can alter the number of concurrent instances of splunk-optimize by changing the value set for &lt;CODE&gt;maxConcurrentOptimizes&lt;/CODE&gt; in &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Indexesconf"&gt;indexes.conf&lt;/A&gt; but i dont think you can tell him when to run &lt;BR /&gt;
outside forcing it to run via &lt;CODE&gt;./splunk-optimize &amp;lt;directory&amp;gt;&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2012 19:37:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63948#M22374</guid>
      <dc:creator>MarioM</dc:creator>
      <dc:date>2012-09-18T19:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: splunk-optimize in multi-instance enviroments</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63949#M22375</link>
      <description>&lt;P&gt;I'm not sure maxConcurrentOptimizes will help in my situation since its single optimizes spanning multiple instances.  It seems that a possible ugly solution is to just disable it and cron them staggered but that would take some R&amp;amp;D.  I was hoping there was a way to do it natively.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2012 19:57:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63949#M22375</guid>
      <dc:creator>jfraiberg</dc:creator>
      <dc:date>2012-09-18T19:57:02Z</dc:date>
    </item>
    <item>
      <title>Re: splunk-optimize in multi-instance enviroments</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63950#M22376</link>
      <description>&lt;P&gt;you might want to open a case to splunk support to see if they have a suggestion&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2012 20:01:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/splunk-optimize-in-multi-instance-enviroments/m-p/63950#M22376</guid>
      <dc:creator>MarioM</dc:creator>
      <dc:date>2012-09-18T20:01:11Z</dc:date>
    </item>
  </channel>
</rss>

