<?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 Cluster -&amp;gt; master node and peer node on same machine in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-gt-master-node-and-peer-node-on-same-machine/m-p/62829#M2147</link>
    <description>&lt;P&gt;I have 4 machines (RHEL) and wanted to make 2 clusters (2 peer nodes per cluster) of these.&lt;BR /&gt;
But one thing made me very sad. &lt;BR /&gt;
"Important: The master cannot do double duty as a peer node or a search head, and it cannot reside on the same machine as a peer node or search head."&lt;/P&gt;

&lt;P&gt;Is this really true? How would these instances know of each other if I change the install directory?&lt;BR /&gt;
has anyone tried this approach?&lt;/P&gt;</description>
    <pubDate>Fri, 15 Mar 2013 12:36:02 GMT</pubDate>
    <dc:creator>jtworzydlo</dc:creator>
    <dc:date>2013-03-15T12:36:02Z</dc:date>
    <item>
      <title>Cluster -&gt; master node and peer node on same machine</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-gt-master-node-and-peer-node-on-same-machine/m-p/62829#M2147</link>
      <description>&lt;P&gt;I have 4 machines (RHEL) and wanted to make 2 clusters (2 peer nodes per cluster) of these.&lt;BR /&gt;
But one thing made me very sad. &lt;BR /&gt;
"Important: The master cannot do double duty as a peer node or a search head, and it cannot reside on the same machine as a peer node or search head."&lt;/P&gt;

&lt;P&gt;Is this really true? How would these instances know of each other if I change the install directory?&lt;BR /&gt;
has anyone tried this approach?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2013 12:36:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-gt-master-node-and-peer-node-on-same-machine/m-p/62829#M2147</guid>
      <dc:creator>jtworzydlo</dc:creator>
      <dc:date>2013-03-15T12:36:02Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster -&gt; master node and peer node on same machine</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-gt-master-node-and-peer-node-on-same-machine/m-p/62830#M2148</link>
      <description>&lt;P&gt;Regardless of what may or may not be technically possible, putting more than one role of the cluster onto the same machine makes the system vulnerable to single points of failure. If for example a combined master/peer box goes down there is no master to redistribute the lost buckets.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2013 13:13:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-gt-master-node-and-peer-node-on-same-machine/m-p/62830#M2148</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2013-03-15T13:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster -&gt; master node and peer node on same machine</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Cluster-gt-master-node-and-peer-node-on-same-machine/m-p/62831#M2149</link>
      <description>&lt;P&gt;The main reason we recommend to run each component of clustering (master, peer, search head) on separate server is because we don't want the failure of one component affects the other and bring down the entire cluster. &lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2013 21:26:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Cluster-gt-master-node-and-peer-node-on-same-machine/m-p/62831#M2149</guid>
      <dc:creator>mahamed_splunk</dc:creator>
      <dc:date>2013-03-20T21:26:07Z</dc:date>
    </item>
  </channel>
</rss>

