Splunk Search

collect command taking up significant memory after upgrading

SplunkIsLife
Explorer

After upgrading from 6.6->7.2.4, we started receiving an alert daily that a nightly job was taking memory exceeding our set threshold for a single search. The search used a collect command taking a large index, filtering to a subset of messages, and then collect the results into a smaller index (a 2 line search). It consistently pulls in around 100,000 logs, but takes between 4 minutes and several hours to run - much to our confusion. The longer ones are taking up all the available memory and crashing Splunk. This only started happening after the upgrade. Any thoughts appreciated! Thanks

Tags (1)
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!

Build the Future of Agentic AI: Join the Splunk Agentic Ops Hackathon

AI is changing how teams investigate incidents, detect threats, automate workflows, and build intelligent ...

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...