Splunk's bin/.cache is growing out of proportions. Is there a configuration setting to limit the size?

[arkadyz1]

I have a python script which returns all kinds of images via REST interface by going for some external sites to fetch them first. Apparently, the results of all such requests to the external sites are cached in $SPLUNK_HOME/bin/.cache/. Unfortunately, our requests are constantly changing, so, on one hand, we don't really need that cache much, and, on the other hand, that folder is growing because each request is a new one.

At some point, Splunk stops all searches because the root partition has less than 5G free space. That's how we discovered bin/cache - by running around the whole system with du and looking for the offending folder.

Are there any configuration settings allowing us to cap the size of bin/.cache somehow? I couldn't find anything in Splunk Admin manual.

[arkadyz1 · Accepted solution]

OK, it's confirmed: I copy pasted some code from the Internet, getting an http connection like this:

h = httplib2.Http(".cache", timeout = 10)

(timeout was my addition). Once I removed that ".cache" from the parameters, the files stopped appearing there. A strange thing is: the cache was still populating even for requests with 'cache-control' header set to 'no-cache' (a bug in httplib2?)

Consider this more of a "raising the awareness" post.

[arkadyz1]

I realized that we are using httplib2 and are creating the connection with '.cache' parameter. I'm not completely sure it's the reason, though it may well be...