<?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: Splunk 9.2.0.1 Bug in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682483#M113993</link>
    <description>&lt;P&gt;I can confirm that the problem is fixed on version 9.2.1! I upgraded to version 9.2.1 and those indexers work perfectly without additional configuration!&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Sat, 30 Mar 2024 13:21:48 GMT</pubDate>
    <dc:creator>banaie</dc:creator>
    <dc:date>2024-03-30T13:21:48Z</dc:date>
    <item>
      <title>Splunk 9.2.0.1 Bug</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/681958#M113936</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I have faced a serious problem after upgrading indexers to 9.2.0.1! Occasionally, they stop data flow and sometimes are shown down on cluster master!&lt;/P&gt;&lt;P&gt;I analyzed the problem and it shows this error occasionally:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Search peer indexer-1 has the following message: The index processor has paused data flow. Too many tsidx files in idx=main bucket="/opt/SplunkData/db/defaultdb/hot_v1_13320" , waiting for the splunk-optimize indexing helper to catch up merging them. Ensure reasonable disk space is available, and that I/O write throughput is not compromised. &lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;It worked smooth with same load in lower versions! I think this is a bug in new version or some more configuration is needed!&lt;/P&gt;&lt;P&gt;Finally, I rolled back to 9.1.3 and it now works perfectly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2024 07:08:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/681958#M113936</guid>
      <dc:creator>banaie</dc:creator>
      <dc:date>2024-03-26T07:08:39Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 9.2.0.1 Bug</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682055#M113954</link>
      <description>&lt;P&gt;It might be possible to tweak the indexer queue size and change the indexes.conf settings, as per this other community post:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.splunk.com/t5/Splunk-Enterprise/The-index-processor-has-paused-data-flow-How-to-optimize/m-p/633597" target="_blank"&gt;https://community.splunk.com/t5/Splunk-Enterprise/The-index-processor-has-paused-data-flow-How-to-optimize/m-p/633597&lt;/A&gt;&lt;/P&gt;&lt;P&gt;According to the post it should be fixed in version 9.1, but perhaps something has made the issue resurface.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2024 21:29:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682055#M113954</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-03-26T21:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 9.2.0.1 Bug</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682093#M113957</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/263556"&gt;@marnall&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are right! It is the same problem! But, it was said that it is fixed in 9.1 and I don't have any problem on 9.1.3! However, same bug has re-appeared on 9.2.0.1 again!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 10:31:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682093#M113957</guid>
      <dc:creator>banaie</dc:creator>
      <dc:date>2024-03-27T10:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 9.2.0.1 Bug</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682189#M113969</link>
      <description>&lt;P&gt;Indeed. You could try the workaround. Perhaps it still works.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 21:18:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682189#M113969</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-03-27T21:18:20Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 9.2.0.1 Bug</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682483#M113993</link>
      <description>&lt;P&gt;I can confirm that the problem is fixed on version 9.2.1! I upgraded to version 9.2.1 and those indexers work perfectly without additional configuration!&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 30 Mar 2024 13:21:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-9-2-0-1-Bug/m-p/682483#M113993</guid>
      <dc:creator>banaie</dc:creator>
      <dc:date>2024-03-30T13:21:48Z</dc:date>
    </item>
  </channel>
</rss>

