<?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 resolve error message after indexer went down: &amp;quot;too many tsidx files in bucket&amp;quot;? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-error-message-after-indexer-went-down-quot-too/m-p/373333#M67682</link>
    <description>&lt;P&gt;Additional to that if you see the below ERROR as well you can also increase the value of maxConcurrentOptimizes in indexes.conf for a particular index which is affected or you can set globally to all the indexes depends on your requirement.&lt;/P&gt;

&lt;P&gt;ERROR:&lt;BR /&gt;
04-11-2019 11:01:51.574 +0500 ERROR SplunkOptimize - (child_39286__SplunkOptimize) optimize finished: failed, see rc for more details, dir=C:\Program Files\Splunk\var\lib\splunk_internaldb\db\hot_v1_268, rc=-12 (unsigned 244), errno=0 &lt;/P&gt;

&lt;P&gt;04-11-2019 11:01:51.574 +0500 ERROR SplunkOptimize - (child_39286__SplunkOptimize) merge failed for path=C:\Program Files\Splunk\var\lib\splunk_internaldb\db\hot_v1_268 rc=-12 wrc=-12 errno=0 file=dontknow hint=tsval_id is UINT_MAX in _merge_all_postings]&lt;/P&gt;

&lt;P&gt;Example:&lt;/P&gt;

&lt;P&gt;In indexes.conf&lt;/P&gt;

&lt;P&gt;For particular index:&lt;BR /&gt;
[_internal]&lt;BR /&gt;
maxConcurrentOptimizes = &amp;lt; desired value &amp;gt;&lt;/P&gt;

&lt;P&gt;For all the indexes:&lt;BR /&gt;
[default]&lt;BR /&gt;
maxConcurrentOptimizes = &amp;lt; desigered value &amp;gt;&lt;/P&gt;

&lt;P&gt;maxConcurrentOptimizes = &amp;lt; nonnegative integer &amp;gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;The number of concurrent optimize processes that can run against the hot
DB.&lt;/LI&gt;
&lt;LI&gt;This number should be increased if:

&lt;UL&gt;
&lt;LI&gt;There are always many small tsidx files in the hot DB.&lt;/LI&gt;
&lt;LI&gt;After rolling, there are many tsidx files in warm or cold DB.&lt;/LI&gt;
&lt;/UL&gt;&lt;/LI&gt;
&lt;LI&gt;Must restart splunkd after changing this parameter; index reload will not
suffice.&lt;/LI&gt;
&lt;LI&gt;Highest legal value is 4294967295&lt;/LI&gt;
&lt;LI&gt;Defaults to 6&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Wed, 30 Sep 2020 00:14:00 GMT</pubDate>
    <dc:creator>anaidu_splunk</dc:creator>
    <dc:date>2020-09-30T00:14:00Z</dc:date>
    <item>
      <title>How to resolve error message after indexer went down: "too many tsidx files in bucket"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-error-message-after-indexer-went-down-quot-too/m-p/373331#M67680</link>
      <description>&lt;P&gt;One indexer just went down. As it came up we see the following message for a couple of the indexers -&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;throttled: idx=&amp;lt;idx_name&amp;gt; Throttling indexer, too many tsidx files in bucket='/SplunkIndexData/splunk-indexes/&amp;lt;idx_name&amp;gt;/db/hot_v1_1519'. Is splunk-optimize working? If not, low disk space may be the cause. 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What it is exactly? &lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2017 16:52:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-error-message-after-indexer-went-down-quot-too/m-p/373331#M67680</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-10-03T16:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to resolve error message after indexer went down: "too many tsidx files in bucket"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-error-message-after-indexer-went-down-quot-too/m-p/373332#M67681</link>
      <description>&lt;P&gt;The below errors indicates "high I/O activity of splunk-optimize":&lt;/P&gt;

&lt;P&gt;throttled: idx= Throttling indexer, too many tsidx files in bucket='/SplunkIndexData/splunk-indexes//db/hot_v1_1519'. Is splunk-optimize working? If not, low disk space may be the cause. &lt;/P&gt;

&lt;P&gt;The way to reduce splunk-optimize I/O activity is to increase maxMemMB for index "" which has most of throttling messages and any other index customer is aware of high volume:&lt;/P&gt;

&lt;P&gt;indexes.conf&lt;BR /&gt;
[index_name] &lt;BR /&gt;
maxMemMB=20&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:13:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-error-message-after-indexer-went-down-quot-too/m-p/373332#M67681</guid>
      <dc:creator>mbagali_splunk</dc:creator>
      <dc:date>2020-09-30T00:13:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to resolve error message after indexer went down: "too many tsidx files in bucket"?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-error-message-after-indexer-went-down-quot-too/m-p/373333#M67682</link>
      <description>&lt;P&gt;Additional to that if you see the below ERROR as well you can also increase the value of maxConcurrentOptimizes in indexes.conf for a particular index which is affected or you can set globally to all the indexes depends on your requirement.&lt;/P&gt;

&lt;P&gt;ERROR:&lt;BR /&gt;
04-11-2019 11:01:51.574 +0500 ERROR SplunkOptimize - (child_39286__SplunkOptimize) optimize finished: failed, see rc for more details, dir=C:\Program Files\Splunk\var\lib\splunk_internaldb\db\hot_v1_268, rc=-12 (unsigned 244), errno=0 &lt;/P&gt;

&lt;P&gt;04-11-2019 11:01:51.574 +0500 ERROR SplunkOptimize - (child_39286__SplunkOptimize) merge failed for path=C:\Program Files\Splunk\var\lib\splunk_internaldb\db\hot_v1_268 rc=-12 wrc=-12 errno=0 file=dontknow hint=tsval_id is UINT_MAX in _merge_all_postings]&lt;/P&gt;

&lt;P&gt;Example:&lt;/P&gt;

&lt;P&gt;In indexes.conf&lt;/P&gt;

&lt;P&gt;For particular index:&lt;BR /&gt;
[_internal]&lt;BR /&gt;
maxConcurrentOptimizes = &amp;lt; desired value &amp;gt;&lt;/P&gt;

&lt;P&gt;For all the indexes:&lt;BR /&gt;
[default]&lt;BR /&gt;
maxConcurrentOptimizes = &amp;lt; desigered value &amp;gt;&lt;/P&gt;

&lt;P&gt;maxConcurrentOptimizes = &amp;lt; nonnegative integer &amp;gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;The number of concurrent optimize processes that can run against the hot
DB.&lt;/LI&gt;
&lt;LI&gt;This number should be increased if:

&lt;UL&gt;
&lt;LI&gt;There are always many small tsidx files in the hot DB.&lt;/LI&gt;
&lt;LI&gt;After rolling, there are many tsidx files in warm or cold DB.&lt;/LI&gt;
&lt;/UL&gt;&lt;/LI&gt;
&lt;LI&gt;Must restart splunkd after changing this parameter; index reload will not
suffice.&lt;/LI&gt;
&lt;LI&gt;Highest legal value is 4294967295&lt;/LI&gt;
&lt;LI&gt;Defaults to 6&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:14:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-resolve-error-message-after-indexer-went-down-quot-too/m-p/373333#M67682</guid>
      <dc:creator>anaidu_splunk</dc:creator>
      <dc:date>2020-09-30T00:14:00Z</dc:date>
    </item>
  </channel>
</rss>

