Getting Data In

Are there practical limits to queue sizing on indexers?

twinspop
Influencer

We had an issue with parsing queue filling recently. Our oversized event profile is to blame. To address, I increased our queue size across the board to 100 MB from 50 MB. Is there any reason not to go higher? 1 GB? Given an indexer with unlimited RAM, is there a point of diminishing returns when it comes to queue sizing? Do the different queues have different PoDRs?

terminaloutcome
Path Finder

We've run pretty high queue sizes in the order of multiple gigabytes - but if you've got regular massive queues instead of short-term spikes you're probably focusing on the wrong problem. Ensure that you've sized your servers appropriately for the load, and tune the processing path to make sure you're not unnecessarily holding up data.

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!

Meet Splunk Observability Studio: AI-Assisted OpenTelemetry Instrumentation Without ...

Instrumentation is usually the last step or even an afterthought when building out a project. The feature ...

Federated Search for Cisco Security and Analytics Logging (SAL) is now GA on Splunk ...

Federated Search for Cisco  Security Analytics and Logging (SAL) is now generally available as part of the ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Join us for a demo-driven look at how ...