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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...