<?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 Can you help me with an Issue building a Splunk cluster? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411711#M14750</link>
    <description>&lt;P&gt;I manage a couple of small Splunk clusters, and for the 1st time, I need to build one form scratch. I am testing in our sandbox environment, but when I bring the cluster up, I end up with index issues that can't seem to be resolved.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;cannot fix up search factor as bucket is not serviceable
Cannot fix search count as the bucket hasn't rolled yet.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The above messages show up for every bucket in the _audit and _internal indexes. The build is a fairly simple one: 2 indexer peers, 1 master, and 1 dedicated search head&lt;/P&gt;

&lt;P&gt;1- It's RHEL based&lt;BR /&gt;
2- Install the rpm, 7.0.3 is the version I am playing with&lt;BR /&gt;
3 - Set the firewall rules to allow the traffic&lt;BR /&gt;
4 - /opt/splunk/bin/splunk enable boot-start -user root --accept-license&lt;BR /&gt;
5 - /opt/splunk/bin/splunk start --accept-license&lt;/P&gt;

&lt;P&gt;For the master I run - &lt;CODE&gt;/opt/splunk/bin/splunk edit cluster-config -mode master -replication_factor 2 -search_factor 2 -secret xxx  -cluster_label test&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;For the indexer peers - &lt;CODE&gt;/opt/splunk/bin/splunk edit cluster-config -mode slave -master_uri &lt;A href="https://xx.xxx.xx.xx:8089" target="test_blank"&gt;https://xx.xxx.xx.xx:8089&lt;/A&gt; -replication_port 9887 -secret xxx&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;For the Search head - &lt;CODE&gt;/opt/splunk/bin/splunk edit cluster-config -mode searchhead -master_uri &lt;A href="https://xx.x.xxx.xx:8089" target="test_blank"&gt;https://xx.x.xxx.xx:8089&lt;/A&gt; -secret xxx&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Restart Splunk on the master, then configure the other nodes and restart Splunk.&lt;/P&gt;

&lt;P&gt;Not sure what I am missing or doing wrong.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Feb 2019 19:46:35 GMT</pubDate>
    <dc:creator>a238574</dc:creator>
    <dc:date>2019-02-28T19:46:35Z</dc:date>
    <item>
      <title>Can you help me with an Issue building a Splunk cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411711#M14750</link>
      <description>&lt;P&gt;I manage a couple of small Splunk clusters, and for the 1st time, I need to build one form scratch. I am testing in our sandbox environment, but when I bring the cluster up, I end up with index issues that can't seem to be resolved.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;cannot fix up search factor as bucket is not serviceable
Cannot fix search count as the bucket hasn't rolled yet.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The above messages show up for every bucket in the _audit and _internal indexes. The build is a fairly simple one: 2 indexer peers, 1 master, and 1 dedicated search head&lt;/P&gt;

&lt;P&gt;1- It's RHEL based&lt;BR /&gt;
2- Install the rpm, 7.0.3 is the version I am playing with&lt;BR /&gt;
3 - Set the firewall rules to allow the traffic&lt;BR /&gt;
4 - /opt/splunk/bin/splunk enable boot-start -user root --accept-license&lt;BR /&gt;
5 - /opt/splunk/bin/splunk start --accept-license&lt;/P&gt;

&lt;P&gt;For the master I run - &lt;CODE&gt;/opt/splunk/bin/splunk edit cluster-config -mode master -replication_factor 2 -search_factor 2 -secret xxx  -cluster_label test&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;For the indexer peers - &lt;CODE&gt;/opt/splunk/bin/splunk edit cluster-config -mode slave -master_uri &lt;A href="https://xx.xxx.xx.xx:8089" target="test_blank"&gt;https://xx.xxx.xx.xx:8089&lt;/A&gt; -replication_port 9887 -secret xxx&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;For the Search head - &lt;CODE&gt;/opt/splunk/bin/splunk edit cluster-config -mode searchhead -master_uri &lt;A href="https://xx.x.xxx.xx:8089" target="test_blank"&gt;https://xx.x.xxx.xx:8089&lt;/A&gt; -secret xxx&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Restart Splunk on the master, then configure the other nodes and restart Splunk.&lt;/P&gt;

&lt;P&gt;Not sure what I am missing or doing wrong.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 19:46:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411711#M14750</guid>
      <dc:creator>a238574</dc:creator>
      <dc:date>2019-02-28T19:46:35Z</dc:date>
    </item>
    <item>
      <title>Re: Can you help me with an Issue building a Splunk cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411712#M14751</link>
      <description>&lt;P&gt;You are building an index cluster with 1 node and configure &lt;CODE&gt;replication_factor=2&lt;/CODE&gt; , this cannot work. You would need at least 2 nodes to make it work.&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 22:52:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411712#M14751</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2019-02-28T22:52:21Z</dc:date>
    </item>
    <item>
      <title>Re: Can you help me with an Issue building a Splunk cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411713#M14752</link>
      <description>&lt;P&gt;Its got 4 nodes 1 for each function  2 indexer peers, 1 master, and 1 dedicated search head&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 13:07:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411713#M14752</guid>
      <dc:creator>a238574</dc:creator>
      <dc:date>2019-03-01T13:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: Can you help me with an Issue building a Splunk cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411714#M14753</link>
      <description>&lt;P&gt;The steps are the same for each node except for the cluster config  command&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 13:10:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411714#M14753</guid>
      <dc:creator>a238574</dc:creator>
      <dc:date>2019-03-01T13:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: Can you help me with an Issue building a Splunk cluster?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411715#M14754</link>
      <description>&lt;P&gt;Found the issue. I had copied the rhel firewall rules from another splunk env that had modified the replication port from 9887 to 8080. Once I fixed the rules the index issues were automatically fixed.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Mar 2019 16:17:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Can-you-help-me-with-an-Issue-building-a-Splunk-cluster/m-p/411715#M14754</guid>
      <dc:creator>a238574</dc:creator>
      <dc:date>2019-03-07T16:17:43Z</dc:date>
    </item>
  </channel>
</rss>

