<?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: The current bundle directory contains a large lookup file that might cause bundle replication fail - delta in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603124#M209896</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hi Giuseppe&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;my problem is rather that the delta is shown in the message, not the bundle. So my question is - should I look for a big file in the delta and what is considered a bid file for the delta? Or should I still look for big files in the bundle? I can't identify which file is causing the problem.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Daisy&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 24 Jun 2022 08:12:57 GMT</pubDate>
    <dc:creator>daisy</dc:creator>
    <dc:date>2022-06-24T08:12:57Z</dc:date>
    <item>
      <title>How to resolve:The current bundle directory contains a large lookup file that might cause bundle replication fail- delta</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603090#M209883</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;I keep getting a message that the current bundle directory contains a large lookup file and the specified file is a delta under /opt/splunk/var/run. I read that the max_memtable_bytes determines the maximum size of lookups. But how about the delta? What delta size is too large? Or should I rather be looking at the largest lookups in the bundle to resolve the problem? Do you have any tipps on how to resolve this?Thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 15:46:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603090#M209883</guid>
      <dc:creator>daisy</dc:creator>
      <dc:date>2022-06-24T15:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: The current bundle directory contains a large lookup file that might cause bundle replication fail - delta</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603121#M209895</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231409"&gt;@daisy&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you could enlarge this parameter in limits.conf, but I think that the best solution is to blacklist this lookup in bundle, you can do this following the instructions at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.0/DistSearch/Limittheknowledgebundlesize#Eliminate_files_from_the_knowledge_bundle" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.0/DistSearch/Limittheknowledgebundlesize#Eliminate_files_from_the_knowledge_bundle&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 07:17:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603121#M209895</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-06-24T07:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: The current bundle directory contains a large lookup file that might cause bundle replication fail - delta</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603124#M209896</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi Giuseppe&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;my problem is rather that the delta is shown in the message, not the bundle. So my question is - should I look for a big file in the delta and what is considered a bid file for the delta? Or should I still look for big files in the bundle? I can't identify which file is causing the problem.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Daisy&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 08:12:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603124#M209896</guid>
      <dc:creator>daisy</dc:creator>
      <dc:date>2022-06-24T08:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: The current bundle directory contains a large lookup file that might cause bundle replication fail - delta</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603126#M209897</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231409"&gt;@daisy&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;in the message you should have the indication of the too large bundle, anyway, you could see in the Search Head Captain, the dimension of each app and find the too large bundle.&lt;/P&gt;&lt;P&gt;ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 08:20:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603126#M209897</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-06-24T08:20:41Z</dc:date>
    </item>
    <item>
      <title>Re: The current bundle directory contains a large lookup file that might cause bundle replication fail - delta</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603129#M209898</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;gcusello,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;only the delta is mentioned in the message. That's why I am bit confused - should I be looking at the bundle instead? The delta is just the new changes made, while the bundle contains all lookups, as far as I know.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Daisy&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 08:30:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603129#M209898</guid>
      <dc:creator>daisy</dc:creator>
      <dc:date>2022-06-24T08:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: The current bundle directory contains a large lookup file that might cause bundle replication fail - delta</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603130#M209899</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;even the SH normally sends only delta there will be a situations when it needs to send the whole lookup. If it cannot sent even delta how it can send the whole lookup? Or if the delta is actually the whole lookup? For that reason I’m totally agree with&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;what is the best way to go forward.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 08:34:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-resolve-The-current-bundle-directory-contains-a-large/m-p/603130#M209899</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2022-06-24T08:34:16Z</dc:date>
    </item>
  </channel>
</rss>

