<?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: How to restore the corrupted buckets in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/524968#M4584</link>
    <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a clustered indexers in a multi site environment. DO I need to shutdown the full cluster to run the&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;fsck command?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 15 Oct 2020 23:05:39 GMT</pubDate>
    <dc:creator>msplunk33</dc:creator>
    <dc:date>2020-10-15T23:05:39Z</dc:date>
    <item>
      <title>HHow to restore the corrupted buckets</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/524747#M4579</link>
      <description>&lt;P&gt;I have a&amp;nbsp; issue with one index in which the bucket is corrupted and I lost logs from this index for a period of time. How can I fix this.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2020 00:17:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/524747#M4579</guid>
      <dc:creator>msplunk33</dc:creator>
      <dc:date>2020-10-15T00:17:01Z</dc:date>
    </item>
    <item>
      <title>Re: HHow to restore the corrupted buckets</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/524840#M4582</link>
      <description>&lt;P&gt;Try running Splunk's fsck command.&amp;nbsp; See&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/Latest/Troubleshooting/CommandlinetoolsforusewithSupport#fsck" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/Latest/Troubleshooting/CommandlinetoolsforusewithSupport#fsck&lt;/A&gt;&amp;nbsp;and&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.6/Indexer/Bucketissues" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.6/Indexer/Bucketissues&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2020 12:38:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/524840#M4582</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-10-15T12:38:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to restore the corrupted buckets</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/524968#M4584</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a clustered indexers in a multi site environment. DO I need to shutdown the full cluster to run the&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;fsck command?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2020 23:05:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/524968#M4584</guid>
      <dc:creator>msplunk33</dc:creator>
      <dc:date>2020-10-15T23:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to restore the corrupted buckets</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/525051#M4585</link>
      <description>&lt;P&gt;You only need to stop the indexer on which the corrupt bucket resides.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Oct 2020 12:47:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/525051#M4585</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-10-16T12:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to restore the corrupted buckets</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/525147#M4588</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I shutdown one node alone can this case&amp;nbsp; search factor and replication factor met failure? Will the data generated during the shutdown period will be replicated to this nodes after we bring it up?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Oct 2020 21:53:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/525147#M4588</guid>
      <dc:creator>msplunk33</dc:creator>
      <dc:date>2020-10-16T21:53:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to restore the corrupted buckets</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/525260#M4589</link>
      <description>&lt;P&gt;Shutting down an indexer may affect the ability for Splunk for maintain the desired search and replication factors.&amp;nbsp; It depends on your architecture and the specific RF/SF settings.&amp;nbsp; It will only be temporary, though.&amp;nbsp; Once the indexer comes back up the RF and SF will resolve themselves.&lt;/P&gt;&lt;P&gt;Data onboarded while the indexer is down will be stored on the other indexer(s) and will be replicated to the restarted node, if necessary.&lt;/P&gt;</description>
      <pubDate>Sun, 18 Oct 2020 21:52:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/HHow-to-restore-the-corrupted-buckets/m-p/525260#M4589</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-10-18T21:52:13Z</dc:date>
    </item>
  </channel>
</rss>

