<?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: kvstore mongo directory is very large in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400746#M71366</link>
    <description>&lt;P&gt;-rw-------. 1 root root 536608768 feb 17 07:12 s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.29&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 07:13 s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.27&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 07:13 s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.31&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 07:13 s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.30&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 23:22:14 GMT</pubDate>
    <dc:creator>aecruzp</dc:creator>
    <dc:date>2020-09-29T23:22:14Z</dc:date>
    <item>
      <title>kvstore mongo directory is very large</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400745#M71365</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;

&lt;P&gt;I have a issue, we migrate Splunk from 6.6.11 to 7.2.3 in both cluster (SH and Indexer), on indexer we aply migration migration-kvstore, but not on the SH nodes.&lt;/P&gt;

&lt;P&gt;The mongo (/home/splunk/splunk/var/lib/splunk/kvstore/mongo)  directory have 350 GB ocuppied of the hard disk, and We are critical.&lt;BR /&gt;
On the log file say (many lines):&lt;BR /&gt;
 2019-02-18T15:17:11.083Z I STORAGE  [initandlisten] Found drop-pending namespace s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.system.drop&lt;BR /&gt;
i2713t-1.c with drop optime { ts: Timestamp(1549620824, 2713), t: -1 }&lt;BR /&gt;
 2019-02-18T15:17:11.083Z I STORAGE  [initandlisten] Found drop-pending namespace s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.system.drop&lt;/P&gt;

&lt;P&gt;An the directory living this files (and many more):&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 19:33 s_monitoDjADiK3LuYveVmB44TZEiI13_DATA_GI8XK1TVzglQkuXOSwiJtOFXl.636&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 20:03 s_monitoDjADiK3LuYveVmB44TZEiI13_DATA_GI8XK1TVzglQkuXOSwiJtOFXl.637&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 20:33 s_monitoDjADiK3LuYveVmB44TZEiI13_DATA_GI8XK1TVzglQkuXOSwiJtOFXl.638&lt;/P&gt;

&lt;P&gt;its possible delete with linux command?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 23:22:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400745#M71365</guid>
      <dc:creator>aecruzp</dc:creator>
      <dc:date>2020-09-29T23:22:11Z</dc:date>
    </item>
    <item>
      <title>Re: kvstore mongo directory is very large</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400746#M71366</link>
      <description>&lt;P&gt;-rw-------. 1 root root 536608768 feb 17 07:12 s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.29&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 07:13 s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.27&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 07:13 s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.31&lt;BR /&gt;
-rw-------. 1 root root 536608768 feb 17 07:13 s_monitoDjADiK3LuYveVmB44TZEiI13_OBJ_GExkG7i403ybeNVt3NN3M3U4J4.30&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 23:22:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400746#M71366</guid>
      <dc:creator>aecruzp</dc:creator>
      <dc:date>2020-09-29T23:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: kvstore mongo directory is very large</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400747#M71367</link>
      <description>&lt;P&gt;We also see this. Exact same size. Same splunk version (7.2.3)&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 07:36:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400747#M71367</guid>
      <dc:creator>agneticdk</dc:creator>
      <dc:date>2019-03-25T07:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: kvstore mongo directory is very large</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400748#M71368</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;

&lt;P&gt;Just saw this for 7.2.5, fixed issues in release notes:&lt;/P&gt;

&lt;P&gt;2019-03-07  SPL-167347, SPL-165968  Frequent searches with outputlookup may trigger highly increased KV Store storage usage or in some cases crash of the mongod process&lt;/P&gt;

&lt;P&gt;André&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 07:38:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/kvstore-mongo-directory-is-very-large/m-p/400748#M71368</guid>
      <dc:creator>agneticdk</dc:creator>
      <dc:date>2019-03-25T07:38:33Z</dc:date>
    </item>
  </channel>
</rss>

