<?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: Max Value for bucket ID in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76730#M2640</link>
    <description>&lt;P&gt;It's an issue indeed. When we append some digits to avoid collisions, we must choose a big number (eg. 1000), but there indeed is a limit, and the bucket dirs beyond that limit are not included in .bucketManifest and not sought. And there is even no warning in logs.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Apr 2018 12:53:14 GMT</pubDate>
    <dc:creator>znaesh</dc:creator>
    <dc:date>2018-04-10T12:53:14Z</dc:date>
    <item>
      <title>Max Value for bucket ID</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76727#M2637</link>
      <description>&lt;P&gt;I haven't been able to find this in the docs. The bucket ID is the last number in the name of a bucket directory. For example, 2768 is the bucket ID in the following folder name.&lt;/P&gt;

&lt;P&gt;e.g. db_1363148387_1363078186_2768&lt;/P&gt;

&lt;P&gt;To resolve bucket ID conflicts, we frequently add a digit to the ends of the filenames. If we do this too often, the bucket IDs could get large. &lt;/P&gt;

&lt;P&gt;Does anyone know the maximum value that the bucket ID can have?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2013 17:58:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76727#M2637</guid>
      <dc:creator>reed_kelly</dc:creator>
      <dc:date>2013-03-27T17:58:15Z</dc:date>
    </item>
    <item>
      <title>Re: Max Value for bucket ID</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76728#M2638</link>
      <description>&lt;P&gt;good question.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2013 22:12:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76728#M2638</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2013-03-27T22:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: Max Value for bucket ID</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76729#M2639</link>
      <description>&lt;P&gt;found myself asking this question earlier today -- same. i'm interested in knowing the answer. &lt;/P&gt;</description>
      <pubDate>Fri, 08 Aug 2014 23:43:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76729#M2639</guid>
      <dc:creator>w531t4</dc:creator>
      <dc:date>2014-08-08T23:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: Max Value for bucket ID</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76730#M2640</link>
      <description>&lt;P&gt;It's an issue indeed. When we append some digits to avoid collisions, we must choose a big number (eg. 1000), but there indeed is a limit, and the bucket dirs beyond that limit are not included in .bucketManifest and not sought. And there is even no warning in logs.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Apr 2018 12:53:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76730#M2640</guid>
      <dc:creator>znaesh</dc:creator>
      <dc:date>2018-04-10T12:53:14Z</dc:date>
    </item>
    <item>
      <title>Re: Max Value for bucket ID</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76731#M2641</link>
      <description>&lt;P&gt;On Splunk 7.0.1, *nix, x86_64, single-instance, the bucket id: &lt;CODE&gt;db_1521417585_1518757502_999999999&lt;/CODE&gt; was searchable at the cli, but search failed at &lt;CODE&gt;db_1521417585_1518757502_9999999991&lt;/CODE&gt;. &lt;BR /&gt;
The only log entry I found notable and consistent required DEBUG mode:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;04–11-2018 19:20:07.650 +0000 DEBUG DatabaseDirectoryManager - Skipping path='/opt/splunk/var/lib/splunk/defaultdb/db/db_1521417585_1518757502_9999999991'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Additional errors might be noted elsewhere, but I didn't catch them.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 18:58:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76731#M2641</guid>
      <dc:creator>ekost</dc:creator>
      <dc:date>2020-09-29T18:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: Max Value for bucket ID</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76732#M2642</link>
      <description>&lt;P&gt;The bucket ID has a theoretical maximum of 2,147,483,647 (it's an int, so 2^31).&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2020 00:31:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Max-Value-for-bucket-ID/m-p/76732#M2642</guid>
      <dc:creator>msearles_splunk</dc:creator>
      <dc:date>2020-01-16T00:31:34Z</dc:date>
    </item>
  </channel>
</rss>

