Splunk Search

Large lookup files.

drussell88
Explorer

I am getting a warning in my splunkd.log for DistributedBundleReplicationManger.
03-15-2013 08:44:28.028 -0400 WARN DistributedBundleReplicationManager - bundle replication to 1 peer(s) took too long (29578ms), bundle file size=64480KB, replication_id=1363351438.
I read that this may be caused by a large look up file. What is this file they are talking about and where do I find it? I am getting this error about once a minute and it is always the same size, so I am assuming it is the same file.

Tags (1)
0 Karma

Strype
Path Finder

Are you looking for all lookup files?

Manager» Lookups» Lookup table files

Likely a csv file used in a search. The knowledge bundle can be found at Splunk Home>var>run>searchpeers>(latest).bundle (that is a file so replace > with backslash), on the search peer. It'll be in there along with every other one you have.

I'm having a similar problem except that mine is past the warn stage.

martin_mueller
SplunkTrust
SplunkTrust

Your bundle is 64MB, so I guess there is 63MB worth of lookup files somewhere in /lookups of some distributed app.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...