This is a known bug (SPL-140831) were Splunk dose not clean up $SPLUNK_HOME/var/run/searchpeers.
This issue is caused when a lookup exceeds the maxmemtablebytes settings in limits.conf.
Please refer below document for more details:
We need to Increase "maxmemtablebytes" under [lookup] inside limits.conf , so that the largest lookup won't get indexed.
Thanks for sharing. You should accept this as the answer so future Splunkers can see how to resolve the issue
I am running version 7.2.6 and I have this issue as well. I did the search for lookups and did not get anything back. As far as I know, my customers are not using them at the moment. I am having a daily issue with disk space due to the bundles not being removed. Is there a way to keep the .bundle files down to only 3 at max at a time? Or something like that. I really don't want to have to delete the indexers (We have six) everytime we reach spacing issues.