<?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: Heavy forwarder as cluster master in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140264#M28791</link>
    <description>&lt;P&gt;The master is designed to function solely as the cluster manager. But I have no issues configuring it to monitor certain path and forwarding it to the indexers in the cluster. So it will still work&lt;/P&gt;</description>
    <pubDate>Sun, 12 Apr 2015 06:10:18 GMT</pubDate>
    <dc:creator>psow_splunk</dc:creator>
    <dc:date>2015-04-12T06:10:18Z</dc:date>
    <item>
      <title>Heavy forwarder as cluster master</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140260#M28787</link>
      <description>&lt;P&gt;Hello splunkers!&lt;/P&gt;

&lt;P&gt;It is possible to configure heavy forwarder as cluster master? &lt;BR /&gt;
My heavy forvarder forward all data to peers, not indexing external data.&lt;/P&gt;

&lt;P&gt;Best regards,&lt;BR /&gt;
Roman&lt;/P&gt;</description>
      <pubDate>Sat, 29 Nov 2014 19:53:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140260#M28787</guid>
      <dc:creator>ryastrebov</dc:creator>
      <dc:date>2014-11-29T19:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy forwarder as cluster master</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140261#M28788</link>
      <description>&lt;P&gt;You should not use the heavy forwarder as a cluster master, although I suppose it is technically &lt;EM&gt;possible&lt;/EM&gt;.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Nov 2014 08:11:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140261#M28788</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-11-30T08:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy forwarder as cluster master</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140262#M28789</link>
      <description>&lt;P&gt;Why should not I do it?&lt;/P&gt;</description>
      <pubDate>Sun, 30 Nov 2014 09:30:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140262#M28789</guid>
      <dc:creator>ryastrebov</dc:creator>
      <dc:date>2014-11-30T09:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy forwarder as cluster master</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140263#M28790</link>
      <description>&lt;P&gt;According to the documentation: "The master has the sole function of managing the other cluster nodes."&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Indexer"&gt;Managing Indexers and Clusters of Indexers&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Dec 2014 21:02:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140263#M28790</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-12-01T21:02:01Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy forwarder as cluster master</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140264#M28791</link>
      <description>&lt;P&gt;The master is designed to function solely as the cluster manager. But I have no issues configuring it to monitor certain path and forwarding it to the indexers in the cluster. So it will still work&lt;/P&gt;</description>
      <pubDate>Sun, 12 Apr 2015 06:10:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140264#M28791</guid>
      <dc:creator>psow_splunk</dc:creator>
      <dc:date>2015-04-12T06:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy forwarder as cluster master</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140265#M28792</link>
      <description>&lt;P&gt;Technically you can do this.&lt;/P&gt;

&lt;P&gt;However, you need to understand the workload on the HF. If the HF starts to get overtaxed, there will be impact to your cluster in terms of maintaining SF and RF across all the indexers.&lt;/P&gt;

&lt;P&gt;As long as you are aware of this, and keep your resources on the HF in check, this can be done. However, this is against Splunk best practices.&lt;/P&gt;</description>
      <pubDate>Sun, 12 Apr 2015 12:00:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Heavy-forwarder-as-cluster-master/m-p/140265#M28792</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2015-04-12T12:00:06Z</dc:date>
    </item>
  </channel>
</rss>

