Splunk Search

StatsBuffer::read: Row is too large for StatsBuffer, resizing buffer

joemcmahon
Explorer

When performing a query that creates a summary report, the associated search.log file shows:
ResultsCollationProcessor - writing remote_event_providers.csv to disk.

Then two hours later reports:

StatsBuffer::read: Row is too large for StatsBuffer, resizing buffer.  row_size=77060 needed_space=11536 free_space=153653063

This is soon followed by lots of ~min-by-min output of:

SummaryIndexProcessor - Using tmp_file=/opt/splunk/..../RMD....tmp messages.

What might be happening in that two hour window?  We are running Splunk Enterprise 9.1.1 under Linux.

@koronb_splunk @C_Mooney 

Labels (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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...