<?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: Deployment Server and Replication Master in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Deployment-Server-and-Replication-Master/m-p/96519#M3560</link>
    <description>&lt;P&gt;The recommended approach is to use replication master to control all the indexers.&lt;/P&gt;

&lt;P&gt;You can use option #2 as well, but you need to make sure that the DS doesn't restart replication master after pushing the configs.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Feb 2013 23:33:23 GMT</pubDate>
    <dc:creator>mahamed_splunk</dc:creator>
    <dc:date>2013-02-20T23:33:23Z</dc:date>
    <item>
      <title>Deployment Server and Replication Master</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Deployment-Server-and-Replication-Master/m-p/96518#M3559</link>
      <description>&lt;P&gt;Hi Gurus~!&lt;/P&gt;

&lt;P&gt;We understand managing INDEXERs should be done by the replication master.  But when there are so many indexers to manage, like 50+ indexers and 5+ replication master across 5 continent, it makes us curious if we can use deployment server to manage replication master so those masters can distrubute application.&lt;/P&gt;

&lt;P&gt;I am sure this is not a common challenge due to the size of the deployment, but technically what would be feasible.  I would appreciate expert's recommendations.&lt;/P&gt;

&lt;P&gt;In order to simplify multi splunk cluster environment,  ( like 5 masters, and 50+ indexers )&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Only way to manage is just at each 5 replication cluster's master.&lt;/LI&gt;
&lt;LI&gt;Yes, those cluster masters can be controlled via deployment server so that they then deploly apps down to the indexers in cluster environment.&lt;/LI&gt;
&lt;LI&gt;Using Splunk deployment server is not a good idea. Rather recommend other deployment technology like puppet of chief.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Appreciate experts feedback on above 3 choices.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2013 12:28:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Deployment-Server-and-Replication-Master/m-p/96518#M3559</guid>
      <dc:creator>clyde772</dc:creator>
      <dc:date>2013-01-23T12:28:22Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment Server and Replication Master</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Deployment-Server-and-Replication-Master/m-p/96519#M3560</link>
      <description>&lt;P&gt;The recommended approach is to use replication master to control all the indexers.&lt;/P&gt;

&lt;P&gt;You can use option #2 as well, but you need to make sure that the DS doesn't restart replication master after pushing the configs.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Feb 2013 23:33:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Deployment-Server-and-Replication-Master/m-p/96519#M3560</guid>
      <dc:creator>mahamed_splunk</dc:creator>
      <dc:date>2013-02-20T23:33:23Z</dc:date>
    </item>
  </channel>
</rss>

