Splunk Search

collect command taking up significant memory after upgrading


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
Get Updates on the Splunk Community!

Ready, Set, SOAR: How Utility Apps Can Up Level Your Playbooks!

 WATCH NOW Powering your capabilities has never been so easy with ready-made Splunk® SOAR Utility Apps. Parse ...

DevSecOps: Why You Should Care and How To Get Started

 WATCH NOW In this Tech Talk we will talk about what people mean by DevSecOps and deep dive into the different ...

Introducing Ingest Actions: Filter, Mask, Route, Repeat

WATCH NOW Ingest Actions (IA) is the best new way to easily filter, mask and route your data in Splunk® ...