<?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 to distribute Distributed Search configuration using a deployer for a Search Head Cluster? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261189#M9930</link>
    <description>&lt;P&gt;You actually configure each search head independently when it comes to distsearch.conf.  You dont do it by app.&lt;/P&gt;

&lt;P&gt;/opt/splunk/etc/system/local/distsearch.conf &amp;lt;--- will always take precedence over any distsearch.conf because it gets the highest priority&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.0/Admin/Wheretofindtheconfigurationfiles"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.0/Admin/Wheretofindtheconfigurationfiles&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;This means you MUST configure it on each search head independently and not via deployment app from the deployer:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/admin/Distsearchconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/admin/Distsearchconf&lt;/A&gt;&lt;/P&gt;

&lt;H1&gt;To set custom configurations, place a distsearch.conf in $SPLUNK_HOME/etc/system/local/.&lt;/H1&gt;

&lt;H1&gt;For examples, see distsearch.conf.example. You must restart Splunk to enable configurations.&lt;/H1&gt;</description>
    <pubDate>Thu, 26 May 2016 19:54:52 GMT</pubDate>
    <dc:creator>jkat54</dc:creator>
    <dc:date>2016-05-26T19:54:52Z</dc:date>
    <item>
      <title>How to distribute Distributed Search configuration using a deployer for a Search Head Cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261185#M9926</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;We recently set up a SH Cluster which includes 3 members and one deployer. Basic replication seems to be working fine(tested by creating a dashboard on one member), but running into issues when deploying configuration changes. What are the best practices when it comes to deploy a system configuration, e.g. distributed search peer's, from the Deployer to all the SH members?&lt;/P&gt;

&lt;P&gt;If I understood the steps correctly, the only way to deploy anything from a deployer is to create an app under &lt;CODE&gt;/opt/splunk/etc/shcluster/apps&lt;/CODE&gt;. &lt;BR /&gt;
For this, I created a new folder called "configuration" and copied distsearch.conf from &lt;CODE&gt;/opt/splunk/etc/system/local/distsearch.conf&lt;BR /&gt;
&lt;/CODE&gt;&lt;BR /&gt;
Deployment was initiated using &lt;CODE&gt;splunk apply shcluster-bundle&lt;/CODE&gt;. I can see the changes were accepted on the SH Member under &lt;CODE&gt;/opt/splunk/etc/apps/configuration&lt;/CODE&gt;, but SH member is still unable to search any peer. Most likely these changes did not take effect. &lt;BR /&gt;
Is this a wrong way to deploy any system changes using deployer?&lt;/P&gt;

&lt;P&gt;Please advise.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;~Abhi&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2016 16:12:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261185#M9926</guid>
      <dc:creator>att35</dc:creator>
      <dc:date>2016-05-23T16:12:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to distribute Distributed Search configuration using a deployer for a Search Head Cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261186#M9927</link>
      <description>&lt;OL&gt;
&lt;LI&gt;Check if your search heads restarted after receiving new distsearch.conf.&lt;/LI&gt;
&lt;LI&gt;If they did, check the status of search peers from Settings-&amp;gt;Distributed Search-&amp;gt;Search peers. The peers might be saying failed status due to authentication. Open each one of them and provide admin credentials.&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Mon, 23 May 2016 16:17:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261186#M9927</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-05-23T16:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to distribute Distributed Search configuration using a deployer for a Search Head Cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261187#M9928</link>
      <description>&lt;P&gt;You need to create Folder structure like this on Deployer &lt;CODE&gt;/opt/splunk/etc/apps/configuration/local/&lt;/CODE&gt; and then copy distsearch.conf in that folder. After that push the bundle from deployer.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Harshil&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2016 16:23:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261187#M9928</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2016-05-23T16:23:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to distribute Distributed Search configuration using a deployer for a Search Head Cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261188#M9929</link>
      <description>&lt;P&gt;Thank you.&lt;/P&gt;

&lt;P&gt;We checked the members and they did in fact need the credentials to be re-entered. Once that was done it was all set and each member was able to query the pool.&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2016 19:43:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261188#M9929</guid>
      <dc:creator>att35</dc:creator>
      <dc:date>2016-05-26T19:43:53Z</dc:date>
    </item>
    <item>
      <title>Re: How to distribute Distributed Search configuration using a deployer for a Search Head Cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261189#M9930</link>
      <description>&lt;P&gt;You actually configure each search head independently when it comes to distsearch.conf.  You dont do it by app.&lt;/P&gt;

&lt;P&gt;/opt/splunk/etc/system/local/distsearch.conf &amp;lt;--- will always take precedence over any distsearch.conf because it gets the highest priority&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.0/Admin/Wheretofindtheconfigurationfiles"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.0/Admin/Wheretofindtheconfigurationfiles&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;This means you MUST configure it on each search head independently and not via deployment app from the deployer:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/admin/Distsearchconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/admin/Distsearchconf&lt;/A&gt;&lt;/P&gt;

&lt;H1&gt;To set custom configurations, place a distsearch.conf in $SPLUNK_HOME/etc/system/local/.&lt;/H1&gt;

&lt;H1&gt;For examples, see distsearch.conf.example. You must restart Splunk to enable configurations.&lt;/H1&gt;</description>
      <pubDate>Thu, 26 May 2016 19:54:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-distribute-Distributed-Search-configuration-using-a/m-p/261189#M9930</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-05-26T19:54:52Z</dc:date>
    </item>
  </channel>
</rss>

