<?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: Error about bloomfilter not built in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Error-about-bloomfilter-not-built/m-p/47584#M6989</link>
    <description>&lt;P&gt;Please disregard this message, his severity is actually misleading, and will be fixed in future release. &lt;/P&gt;

&lt;P&gt;As you can see it contains both a severity of ERROR and INFO :&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;This is initially an INFO message from the bloomfilter module telling that one bloomfilter file creation will be skipped because the bucket had no recent activity. &lt;/LI&gt;
&lt;LI&gt;However the message is catch by the parent process that tags its as an ERROR. &lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;for detail about the bloomfilter : &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.2/Admin/Bloomfilters"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.2/Admin/Bloomfilters&lt;/A&gt; &lt;/P&gt;</description>
    <pubDate>Wed, 09 May 2012 23:53:36 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2012-05-09T23:53:36Z</dc:date>
    <item>
      <title>Error about bloomfilter not built</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Error-about-bloomfilter-not-built/m-p/47583#M6988</link>
      <description>&lt;P&gt;Found this error message in my splunkd.log while rebuilding my indexes.&lt;BR /&gt;
Is it serious ?&lt;/P&gt;

&lt;P&gt;8:33:19.729 AM 05-09-2012 08:33:19.729 -0400 ERROR ProcessTracker - (child_593365__RecoverMetadata) INFO timeinvertedIndex - Not building bloomfilter for db_1313856000_1313856000_385 in main, since it is 232 days past maxBloomBackfillBucketAgehost=EEEP01 &lt;BR /&gt;
| sourcetype=splunkd | source=D:\Program Files\Splunk\var\log\splunk\splunkd.log &lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 11:47:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Error-about-bloomfilter-not-built/m-p/47583#M6988</guid>
      <dc:creator>mataharry</dc:creator>
      <dc:date>2020-09-28T11:47:47Z</dc:date>
    </item>
    <item>
      <title>Re: Error about bloomfilter not built</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Error-about-bloomfilter-not-built/m-p/47584#M6989</link>
      <description>&lt;P&gt;Please disregard this message, his severity is actually misleading, and will be fixed in future release. &lt;/P&gt;

&lt;P&gt;As you can see it contains both a severity of ERROR and INFO :&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;This is initially an INFO message from the bloomfilter module telling that one bloomfilter file creation will be skipped because the bucket had no recent activity. &lt;/LI&gt;
&lt;LI&gt;However the message is catch by the parent process that tags its as an ERROR. &lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;for detail about the bloomfilter : &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.2/Admin/Bloomfilters"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.2/Admin/Bloomfilters&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Wed, 09 May 2012 23:53:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Error-about-bloomfilter-not-built/m-p/47584#M6989</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2012-05-09T23:53:36Z</dc:date>
    </item>
  </channel>
</rss>

