<?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 cluster Hardware upgradation in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280704#M53716</link>
    <description>&lt;P&gt;i had resolved it, in 3 steps.&lt;BR /&gt;
   1.updated restart_timeout stanza,  increased time out to 15 min  in master server server.conf file( master will wait for the peer node to come up till 15 min )&lt;BR /&gt;
  2 set the peer node offline using 'splunk offline'&lt;BR /&gt;
 3 power off the peer node &lt;BR /&gt;
  4 Change the HW settings&lt;BR /&gt;
  5 power on the system&lt;BR /&gt;
  6 wait for replication and search factors met on the master server dashboard  &lt;/P&gt;</description>
    <pubDate>Wed, 08 Feb 2017 18:47:48 GMT</pubDate>
    <dc:creator>svemurilv</dc:creator>
    <dc:date>2017-02-08T18:47:48Z</dc:date>
    <item>
      <title>Indexer cluster Hardware upgradation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280703#M53715</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
 My Splunk environment contains 1 master 6 pears of indexer hosts. I just want to perform the CUP upgrade on my indexer hosts which all are in virtual environment.   i Need to reboot the virtual system after CUP upgrade.&lt;BR /&gt;
  whats the best practices to do this on all 6 indexer pears by minimizing the downtime. &lt;/P&gt;

&lt;P&gt;-Rag&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2017 15:34:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280703#M53715</guid>
      <dc:creator>svemurilv</dc:creator>
      <dc:date>2017-02-07T15:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer cluster Hardware upgradation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280704#M53716</link>
      <description>&lt;P&gt;i had resolved it, in 3 steps.&lt;BR /&gt;
   1.updated restart_timeout stanza,  increased time out to 15 min  in master server server.conf file( master will wait for the peer node to come up till 15 min )&lt;BR /&gt;
  2 set the peer node offline using 'splunk offline'&lt;BR /&gt;
 3 power off the peer node &lt;BR /&gt;
  4 Change the HW settings&lt;BR /&gt;
  5 power on the system&lt;BR /&gt;
  6 wait for replication and search factors met on the master server dashboard  &lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2017 18:47:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280704#M53716</guid>
      <dc:creator>svemurilv</dc:creator>
      <dc:date>2017-02-08T18:47:48Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer cluster Hardware upgradation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280705#M53717</link>
      <description>&lt;P&gt;Hi, you should post your answers as an answer and mark it as "resolved"... so people can see the result better &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
Holger&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2017 22:16:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280705#M53717</guid>
      <dc:creator>hsesterhenn</dc:creator>
      <dc:date>2017-02-08T22:16:21Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer cluster Hardware upgradation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280706#M53718</link>
      <description>&lt;P&gt;For any sort of planned maintenance on your indexer cluster consider using maintenance mode; this way you can prevent bucket fixups from happening in the event that something doesn't come back up in time, etc.&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.5.2/Indexer/Usemaintenancemode"&gt;https://docs.splunk.com/Documentation/Splunk/6.5.2/Indexer/Usemaintenancemode&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2017 23:56:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-cluster-Hardware-upgradation/m-p/280706#M53718</guid>
      <dc:creator>jtacy</dc:creator>
      <dc:date>2017-02-08T23:56:40Z</dc:date>
    </item>
  </channel>
</rss>

