<?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: Indexer VM corrupt in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Indexer-VM-corrupt/m-p/475218#M24382</link>
    <description>&lt;P&gt;Hi Riqbal,&lt;BR /&gt;
Please follow the below steps&lt;/P&gt;

&lt;P&gt;On the new indexer, log into the splunk UI&lt;BR /&gt;
Go to:   Settings-&amp;gt;Indexer Clustering&lt;BR /&gt;
Click "Add cluster to be searched"&lt;/P&gt;

&lt;P&gt;Provide the clustermaster details and the security key. Your new indexer should now be a part of your cluster.&lt;/P&gt;</description>
    <pubDate>Wed, 11 Sep 2019 10:46:13 GMT</pubDate>
    <dc:creator>chinmoya</dc:creator>
    <dc:date>2019-09-11T10:46:13Z</dc:date>
    <item>
      <title>Indexer VM corrupt</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Indexer-VM-corrupt/m-p/475217#M24381</link>
      <description>&lt;P&gt;we have 6 indexers in indexer cluster setup. one of the indexer server, the splunk mount point goes corrupt due to disk space issue. now we mount the new point and install the splunk package on that server . Now how can we join him back to the Indexer cluster. &lt;/P&gt;

&lt;P&gt;Hostname and IP address is same.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2019 07:35:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Indexer-VM-corrupt/m-p/475217#M24381</guid>
      <dc:creator>riqbal47010</dc:creator>
      <dc:date>2019-09-11T07:35:08Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer VM corrupt</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Indexer-VM-corrupt/m-p/475218#M24382</link>
      <description>&lt;P&gt;Hi Riqbal,&lt;BR /&gt;
Please follow the below steps&lt;/P&gt;

&lt;P&gt;On the new indexer, log into the splunk UI&lt;BR /&gt;
Go to:   Settings-&amp;gt;Indexer Clustering&lt;BR /&gt;
Click "Add cluster to be searched"&lt;/P&gt;

&lt;P&gt;Provide the clustermaster details and the security key. Your new indexer should now be a part of your cluster.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2019 10:46:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Indexer-VM-corrupt/m-p/475218#M24382</guid>
      <dc:creator>chinmoya</dc:creator>
      <dc:date>2019-09-11T10:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer VM corrupt</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Indexer-VM-corrupt/m-p/475219#M24383</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;after installing the package I copied the server.conf file from other indexer and just update the name.&lt;/P&gt;

&lt;P&gt;after that i replace the splunk.secret key.&lt;/P&gt;

&lt;P&gt;and we are back in business.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2019 11:45:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Indexer-VM-corrupt/m-p/475219#M24383</guid>
      <dc:creator>riqbal47010</dc:creator>
      <dc:date>2019-09-11T11:45:24Z</dc:date>
    </item>
  </channel>
</rss>

