<?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 Knowledge bundle size issues in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Knowledge-bundle-size-issues/m-p/639358#M9374</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have this error message on the SH in Splunk:&lt;BR /&gt;{&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Knowledge bundle size=3525MB exceeds max limit=2048MB. Distributed searches are running against an outdated knowledge bundle. Please remove/disable files from knowledge bundle or increase maxBundleSize in distsearch.conf.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;What I did is increase the&amp;nbsp;&lt;SPAN&gt;maxBundleSize in distsearch.conf :&lt;BR /&gt;I did this command on the server:&lt;BR /&gt;/opt/splunk/bin/splunk btool distsearch list --debug | grep maxBundleSize&lt;BR /&gt;and the result is:&lt;BR /&gt;/opt/splunk/etc/system/default/distsearch.conf&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; maxBundleSize = 2048&lt;BR /&gt;So inside the&amp;nbsp;/opt/splunk/etc/system/local/distsearch.conf I added the:&lt;BR /&gt;&lt;BR /&gt;[replicationSettings]&lt;BR /&gt;maxBundleSize = 4000&lt;BR /&gt;&lt;BR /&gt;Restarted Splunk, and noticed that the first error message is gone, but a new Yellow warning appeared:&lt;BR /&gt;{&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The current bundle directory contains a large lookup file that might cause bundle replication fail. The path to the directory is /opt/splunk/var/run/InvestBank-SH-1-1681121119-1681121612.delta.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;}&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="muradgh_0-1681123932468.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24851i8B39503530125D0D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="muradgh_0-1681123932468.png" alt="muradgh_0-1681123932468.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;So I went to this path to check what is going on there:&lt;BR /&gt;cd&amp;nbsp;/opt/splunk/var/run&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="muradgh_1-1681124580843.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24852i40F0D23A6B76F55B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="muradgh_1-1681124580843.png" alt="muradgh_1-1681124580843.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I have found 2 large files and one medium.&lt;BR /&gt;Can someone please advise me on what to do past this point?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have found someone posted to check the below search:&lt;BR /&gt;index =_internal sourcetype=splunkd component=Archiver Archiving large_file=*&lt;BR /&gt;| stats count latest(size_in_bytes) by large_file&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="muradgh_2-1681125073509.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24853i405BAFD57399CE7A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="muradgh_2-1681125073509.png" alt="muradgh_2-1681125073509.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I don't know if this has any relation to the subject.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note that my Splunk environment is &lt;STRONG&gt;not&lt;/STRONG&gt; a cluster.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Apr 2023 11:14:18 GMT</pubDate>
    <dc:creator>muradgh</dc:creator>
    <dc:date>2023-04-10T11:14:18Z</dc:date>
    <item>
      <title>Knowledge bundle size issues</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Knowledge-bundle-size-issues/m-p/639358#M9374</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have this error message on the SH in Splunk:&lt;BR /&gt;{&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Knowledge bundle size=3525MB exceeds max limit=2048MB. Distributed searches are running against an outdated knowledge bundle. Please remove/disable files from knowledge bundle or increase maxBundleSize in distsearch.conf.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;What I did is increase the&amp;nbsp;&lt;SPAN&gt;maxBundleSize in distsearch.conf :&lt;BR /&gt;I did this command on the server:&lt;BR /&gt;/opt/splunk/bin/splunk btool distsearch list --debug | grep maxBundleSize&lt;BR /&gt;and the result is:&lt;BR /&gt;/opt/splunk/etc/system/default/distsearch.conf&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; maxBundleSize = 2048&lt;BR /&gt;So inside the&amp;nbsp;/opt/splunk/etc/system/local/distsearch.conf I added the:&lt;BR /&gt;&lt;BR /&gt;[replicationSettings]&lt;BR /&gt;maxBundleSize = 4000&lt;BR /&gt;&lt;BR /&gt;Restarted Splunk, and noticed that the first error message is gone, but a new Yellow warning appeared:&lt;BR /&gt;{&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The current bundle directory contains a large lookup file that might cause bundle replication fail. The path to the directory is /opt/splunk/var/run/InvestBank-SH-1-1681121119-1681121612.delta.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;}&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="muradgh_0-1681123932468.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24851i8B39503530125D0D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="muradgh_0-1681123932468.png" alt="muradgh_0-1681123932468.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;So I went to this path to check what is going on there:&lt;BR /&gt;cd&amp;nbsp;/opt/splunk/var/run&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="muradgh_1-1681124580843.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24852i40F0D23A6B76F55B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="muradgh_1-1681124580843.png" alt="muradgh_1-1681124580843.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I have found 2 large files and one medium.&lt;BR /&gt;Can someone please advise me on what to do past this point?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have found someone posted to check the below search:&lt;BR /&gt;index =_internal sourcetype=splunkd component=Archiver Archiving large_file=*&lt;BR /&gt;| stats count latest(size_in_bytes) by large_file&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="muradgh_2-1681125073509.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24853i405BAFD57399CE7A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="muradgh_2-1681125073509.png" alt="muradgh_2-1681125073509.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I don't know if this has any relation to the subject.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note that my Splunk environment is &lt;STRONG&gt;not&lt;/STRONG&gt; a cluster.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 11:14:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Knowledge-bundle-size-issues/m-p/639358#M9374</guid>
      <dc:creator>muradgh</dc:creator>
      <dc:date>2023-04-10T11:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: Knowledge bundle size issues</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Knowledge-bundle-size-issues/m-p/639363#M9375</link>
      <description>&lt;P&gt;Look inside the large bundle files (they're just tarballs) to see what's making them so large.&amp;nbsp; It's probably one or more huge lookup files.&amp;nbsp; Make sure the lookups are expected to be that big as it's possible a bad search is appending rather than replacing data in the lookup.&lt;/P&gt;&lt;P&gt;If the lookup needs to be that large then remove it from the replication bundle ([repicationDenyList] in distsearch.conf) and distribute it to the indexers via another method.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 12:24:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Knowledge-bundle-size-issues/m-p/639363#M9375</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-04-10T12:24:34Z</dc:date>
    </item>
  </channel>
</rss>

