Getting Data In

What should the indexer queues be?

danielbb
Motivator

After filling the tiny queues on the indexers, we would like to move to bigger queues.

We are thinking about the following -

[queue=AQ]
# Default maxSize = 10MB
maxSize = 200MB

[queue=aggQueue]
# Default maxSize = 1MB
maxSize = 3500MB

[queue=parsingQueue]
# Default maxSize = 6MB
maxSize = 3600MB

[queue=typingQueue]
maxSize = 2100MB

[queue=indexQueue]
maxSize = 4000MB

Does it make sense?

Tags (2)
0 Karma
1 Solution

danielbb
Motivator

Support said -

-- What i assume is occurring based on which Q's are full is that you have a bad regex somewhere, or for a particular source type the event breaking is not working, so for the event breaking not working, the forwarder locks onto an indexer and does not let it loadbalance as it feels it has not reached the end of the event.

And we found out that there was a weird LINE_BREAKER set for a new sourcetype. Removing it and the queues got cleared.

View solution in original post

0 Karma

danielbb
Motivator

Support said -

-- What i assume is occurring based on which Q's are full is that you have a bad regex somewhere, or for a particular source type the event breaking is not working, so for the event breaking not working, the forwarder locks onto an indexer and does not let it loadbalance as it feels it has not reached the end of the event.

And we found out that there was a weird LINE_BREAKER set for a new sourcetype. Removing it and the queues got cleared.

0 Karma
Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...